APRS Packet Errors for KH KOR (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
20260208150005OE3MQK>APN100,TCPIP*,qAC,T2CAEAST:;KH KOR *111111z4812.65N/01618.11EhKlinik Ottakring
20260208153003OE3MQK>APN100,TCPIP*,qAC,T2UKRAINE:;KH KOR *111111z4812.65N/01618.11EhKlinik Ottakring
20260208160004OE3MQK>APN100,TCPIP*,qAC,T2ERFURT:;KH KOR *111111z4812.65N/01618.11EhKlinik Ottakring
20260208163004OE3MQK>APN100,TCPIP*,qAC,T2CHILE:;KH KOR *111111z4812.65N/01618.11EhKlinik Ottakring
20260208170004OE3MQK>APN100,TCPIP*,qAC,T2PANAMA:;KH KOR *111111z4812.65N/01618.11EhKlinik Ottakring
20260208173003OE3MQK>APN100,TCPIP*,qAC,T2ROMANIA:;KH KOR *111111z4812.65N/01618.11EhKlinik Ottakring
20260208180006OE3MQK>APN100,TCPIP*,qAC,T2UKRAINE:;KH KOR *111111z4812.65N/01618.11EhKlinik Ottakring
20260208183004OE3MQK>APN100,TCPIP*,qAC,T2SYDNEY:;KH KOR *111111z4812.65N/01618.11EhKlinik Ottakring
20260208190004OE3MQK>APN100,TCPIP*,qAC,T2UKRAINE:;KH KOR *111111z4812.65N/01618.11EhKlinik Ottakring
20260208193004OE3MQK>APN100,TCPIP*,qAC,T2PANAMA:;KH KOR *111111z4812.65N/01618.11EhKlinik Ottakring
20260208200006OE3MQK>APN100,TCPIP*,qAC,T2BC:;KH KOR *111111z4812.65N/01618.11EhKlinik Ottakring
20260208203004OE3MQK>APN100,TCPIP*,qAC,T2CSNGRAD:;KH KOR *111111z4812.65N/01618.11EhKlinik Ottakring