APRS Packet Errors for EDDN (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
20260208130600	DK6PX>APRS,TCPIP,qAC,T2CSNGRAD:;EDDN 050218z4929.50N/01105.00E^ EDDN 081250Z AUTO VRB02KT 9999 BKN007 BKN034 05/04 Q1008 NOSIG
20260208140545	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;EDDN 050218z4929.50N/01105.00E^ EDDN 081350Z AUTO 32004KT 9999 SCT009 OVC033 05/04 Q1008 NOSIG
20260208150545	DK6PX>APRS,TCPIP,qAC,T2CZECH:;EDDN 050218z4929.50N/01105.00E^ EDDN 081450Z AUTO 35005KT 9999 OVC032 06/04 Q1008 NOSIG
20260208160616	DK6PX>APRS,TCPIP,qAC,T2FRANCE:;EDDN 050218z4929.50N/01105.00E^ EDDN 081550Z AUTO 01007KT 9999 BKN033 06/04 Q1008 NOSIG
20260208170601	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;EDDN 050218z4929.50N/01105.00E^ EDDN 081650Z AUTO 02005KT 350V060 9999 OVC031 05/03 Q1008 NOSIG
20260208180545	DK6PX>APRS,TCPIP,qAC,T2DENMARK:;EDDN 050218z4929.50N/01105.00E^ EDDN 081750Z AUTO 05003KT 9999 OVC031 04/03 Q1008 NOSIG