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
20260209090545	DK6PX>APRS,TCPIP,qAC,T2SWEDEN:;EDDN 050218z4929.50N/01105.00E^ EDDN 090850Z AUTO 09004KT 9999 BKN011 OVC036 04/02 Q1008 NOSIG
20260209100546	DK6PX>APRS,TCPIP,qAC,T2SPAIN:;EDDN 050218z4929.50N/01105.00E^ EDDN 090950Z AUTO 11004KT 080V140 9999 BKN011 OVC034 05/02 Q1008 BECMG SCT010 OVC035
20260209110545	DK6PX>APRS,TCPIP,qAC,T2CSNGRAD:;EDDN 050218z4929.50N/01105.00E^ EDDN 091050Z AUTO 12005KT 090V160 9999 FEW013 OVC032 05/02 Q1008 NOSIG
20260209120545	DK6PX>APRS,TCPIP,qAC,T2DENMARK:;EDDN 050218z4929.50N/01105.00E^ EDDN 091150Z AUTO 10006KT 9999 BKN017 BKN032 06/02 Q1008 NOSIG
20260209130545	DK6PX>APRS,TCPIP,qAC,T2POLNW:;EDDN 050218z4929.50N/01105.00E^ EDDN 091250Z AUTO 13006KT 080V160 9999 SCT020 OVC027 06/01 Q1007 NOSIG
20260209140546	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;EDDN 050218z4929.50N/01105.00E^ EDDN 091350Z AUTO 13008KT 9999 OVC025 06/01 Q1007 NOSIG