APRS Packet Errors for G0BVD-10 (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20260208150259G0BVD-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L4d.{MIBja GLoRa APRS
20260208151759G0BVD-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L4d.{MIBja GLoRa APRS
20260208153259G0BVD-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L4d.{MIBja GLoRa APRS
20260208154759G0BVD-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L4d.{MIBja GLoRa APRS
20260208160259G0BVD-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L4d.{MIBja GLoRa APRS
20260208161759G0BVD-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L4d.{MIBja GLoRa APRS
20260208163259G0BVD-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L4d.{MIBja GLoRa APRS
20260208164759G0BVD-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L4d.{MIBja GLoRa APRS
20260208170259G0BVD-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L4d.{MIBja GLoRa APRS
20260208171759G0BVD-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L4d.{MIBja GLoRa APRS
20260208173259G0BVD-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L4d.{MIBja GLoRa APRS
20260208174759G0BVD-10>APLRG1,TCPIP*,qAC,T2LAUSITZ:!L4d.{MIBja GLoRa APRS