APRS Packet Errors for EA4AAE-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
20260209104751EA4AAE-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:(P>MV*Ra xGLoRa APRS
20260209111751EA4AAE-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:(P>MV*Ra xGLoRa APRS
20260209114751EA4AAE-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:(P>MV*Ra xGLoRa APRS
20260209121751EA4AAE-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:(P>MV*Ra xGLoRa APRS
20260209124751EA4AAE-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:(P>MV*Ra xGLoRa APRS
20260209131751EA4AAE-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:(P>MV*Ra xGLoRa APRS
20260209134751EA4AAE-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:(P>MV*Ra xGLoRa APRS
20260209141752EA4AAE-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:(P>MV*Ra xGLoRa APRS
20260209144752EA4AAE-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:(P>MV*Ra xGLoRa APRS
20260209151752EA4AAE-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:(P>MV*Ra xGLoRa APRS
20260209154752EA4AAE-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:(P>MV*Ra xGLoRa APRS
20260209161752EA4AAE-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:(P>MV*Ra xGLoRa APRS