APRS Packet Errors for G0VZM-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
20260208134447G0VZM-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L32o=N*Tra GHarrogate LoRa APRS iGate Ext=0.55V
20260208141448G0VZM-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L32o=N*Tra GHarrogate LoRa APRS iGate Ext=0.55V
20260208144449G0VZM-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L32o=N*Tra GHarrogate LoRa APRS iGate Ext=0.55V
20260208151450G0VZM-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L32o=N*Tra GHarrogate LoRa APRS iGate Ext=0.55V
20260208154451G0VZM-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L32o=N*Tra GHarrogate LoRa APRS iGate Ext=0.55V
20260208161451G0VZM-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L32o=N*Tra GHarrogate LoRa APRS iGate Ext=0.55V
20260208164452G0VZM-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L32o=N*Tra GHarrogate LoRa APRS iGate Ext=0.55V
20260208171453G0VZM-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L32o=N*Tra GHarrogate LoRa APRS iGate Ext=0.55V
20260208174454G0VZM-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L32o=N*Tra GHarrogate LoRa APRS iGate Ext=0.55V
20260208181454G0VZM-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L32o=N*Tra GHarrogate LoRa APRS iGate Ext=0.55V
20260208184455G0VZM-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L32o=N*Tra GHarrogate LoRa APRS iGate Ext=0.55V
20260208191456G0VZM-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L32o=N*Tra GHarrogate LoRa APRS iGate Ext=0.55V