APRS Packet Errors for G4MHJ-1 (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
20260209105343G4MHJ-1>APN000,TCPIP*,qAC,T2CSNGRAD:@091053z5128.57N/00008.93E_187/000g001t047r000p001P001b10008h95L098eMB63
20260209115345G4MHJ-1>APN000,TCPIP*,qAC,T2SYDNEY:@091153z5128.57N/00008.93E_174/000g001t048r000p001P001b10004h93L102eMB63
20260209125347G4MHJ-1>APN000,TCPIP*,qAC,T2SPAIN:@091253z5128.57N/00008.93E_199/000g001t047r000p001P001b09995h93L107eMB63
20260209135346G4MHJ-1>APN000,TCPIP*,qAC,T2TAS:@091353z5128.57N/00008.93E_167/000g001t046r000p001P001b09988h94L049eMB63
20260209145345G4MHJ-1>APN000,TCPIP*,qAC,T2ERFURT:@091453z5128.57N/00008.93E_182/000g001t045r000p001P001b09980h95L046eMB63
20260209155347G4MHJ-1>APN000,TCPIP*,qAC,T2SYDNEY:@091553z5128.57N/00008.93E_207/000g001t045r000p001P001b09975h95L007eMB63