APRS Packet Errors for ETSI (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
20260208170714	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;ETSI 050218z4842.90N/01132.25E^ ETSI 081620Z AUTO 05006KT 9999 // ////// 06/02 Q1007 ///
20260208180633	DK6PX>APRS,TCPIP,qAC,T2DENMARK:;ETSI 050218z4842.90N/01132.25E^ ETSI 081720Z AUTO 04003KT 9999 // ////// 05/02 Q1007 ///
20260208190637	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;ETSI 050218z4842.90N/01132.25E^ ETSI 081820Z AUTO 07001KT 9999 // ////// 01/00 Q1008 ///
20260208200711	DK6PX>APRS,TCPIP,qAC,T2UKRAINE:;ETSI 050218z4842.90N/01132.25E^ ETSI 081920Z AUTO 07001KT 9999 // ////// M00/M01 Q1008 ///
20260208210642	DK6PX>APRS,TCPIP,qAC,T2ERFURT:;ETSI 050218z4842.90N/01132.25E^ ETSI 082020Z AUTO VRB01KT 9999 // ////// M01/M02 Q1008 ///
20260208220713	DK6PX>APRS,TCPIP,qAC,T2DENMARK:;ETSI 050218z4842.90N/01132.25E^ ETSI 082120Z AUTO 17003KT 9999 // ////// M02/M02 Q1008 ///