APRS Packet Errors for PC9DB-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
20260209090819PC9DB-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L4gOzb,a GLoRa APRS iGate
20260209093819PC9DB-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L4gOzb,a GLoRa APRS iGate
20260209100819PC9DB-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L4gOzb,a GLoRa APRS iGate
20260209103820PC9DB-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L4gOzb,a GLoRa APRS iGate
20260209110820PC9DB-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L4gOzb,a GLoRa APRS iGate
20260209113820PC9DB-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L4gOzb,a GLoRa APRS iGate
20260209120820PC9DB-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L4gOzb,a GLoRa APRS iGate
20260209123820PC9DB-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L4gOzb,a GLoRa APRS iGate
20260209130820PC9DB-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L4gOzb,a GLoRa APRS iGate
20260209133820PC9DB-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L4gOzb,a GLoRa APRS iGate
20260209140820PC9DB-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L4gOzb,a GLoRa APRS iGate
20260209143820PC9DB-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L4gOzb,a GLoRa APRS iGate