APRS Packet Errors for KH STJ (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
20260208133004	OE3MQK>APN100,TCPIP,qAC,T2ROMANIA:;KH STJ 111111z4811.65N/01615.73EhSt. Josef Krankenhaus
20260208140007	OE3MQK>APN100,TCPIP,qAC,T2CHILE:;KH STJ 111111z4811.65N/01615.73EhSt. Josef Krankenhaus
20260208143004	OE3MQK>APN100,TCPIP,qAC,T2ROMANIA:;KH STJ 111111z4811.65N/01615.73EhSt. Josef Krankenhaus
20260208150006	OE3MQK>APN100,TCPIP,qAC,T2UKRAINE:;KH STJ 111111z4811.65N/01615.73EhSt. Josef Krankenhaus
20260208153004	OE3MQK>APN100,TCPIP,qAC,T2DENMARK:;KH STJ 111111z4811.65N/01615.73EhSt. Josef Krankenhaus
20260208160005	OE3MQK>APN100,TCPIP,qAC,T2CSNGRAD:;KH STJ 111111z4811.65N/01615.73EhSt. Josef Krankenhaus
20260208163005	OE3MQK>APN100,TCPIP,qAC,T2SYDNEY:;KH STJ 111111z4811.65N/01615.73EhSt. Josef Krankenhaus
20260208170005	OE3MQK>APN100,TCPIP,qAC,T2BIO:;KH STJ 111111z4811.65N/01615.73EhSt. Josef Krankenhaus
20260208173004	OE3MQK>APN100,TCPIP,qAC,T2SYDNEY:;KH STJ 111111z4811.65N/01615.73EhSt. Josef Krankenhaus
20260208180007	OE3MQK>APN100,TCPIP,qAC,T2SPAIN:;KH STJ 111111z4811.65N/01615.73EhSt. Josef Krankenhaus
20260208183005	OE3MQK>APN100,TCPIP,qAC,T2ROMANIA:;KH STJ 111111z4811.65N/01615.73EhSt. Josef Krankenhaus
20260208190005	OE3MQK>APN100,TCPIP,qAC,T2SPAIN:;KH STJ 111111z4811.65N/01615.73EhSt. Josef Krankenhaus