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
20260208135329G4MHJ-1>APN000,TCPIP*,qAC,T2POLC:@081353z5128.57N/00008.93E_192/000g000t052r000p002P000b10044h87L063eMB63
20260208145329G4MHJ-1>APN000,TCPIP*,qAC,T2SYDNEY:@081453z5128.57N/00008.93E_146/000g004t051r000p001P000b10045h87L098eMB63
20260208155329G4MHJ-1>APN000,TCPIP*,qAC,T2CHILE:@081553z5128.57N/00008.93E_158/000g000t050r000p001P000b10045h89L042eMB63
20260208165329G4MHJ-1>APN000,TCPIP*,qAC,T2DENMARK:@081653z5128.57N/00008.93E_153/000g000t049r000p001P000b10045h91L005eMB63
20260208175329G4MHJ-1>APN000,TCPIP*,qAC,T2TAS:@081753z5128.57N/00008.93E_165/000g000t048r000p000P000b10047h93L000eMB63
20260208185329G4MHJ-1>APN000,TCPIP*,qAC,T2ERFURT:@081853z5128.57N/00008.93E_205/000g000t047r000p000P000b10049h94L000eMB63