APRS Packet Errors for EDDK (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
20260209090543	DK6PX>APRS,TCPIP,qAC,T2SWEDEN:;EDDK 201218z5051.85N/00708.27E^ EDDK 090850Z AUTO 12009KT 090V150 9999 BKN007 02/01 Q1008 BECMG SCT010
20260209100544	DK6PX>APRS,TCPIP,qAC,T2SPAIN:;EDDK 201218z5051.85N/00708.27E^ EDDK 090950Z AUTO 11008KT 080V150 CAVOK 05/01 Q1007 NOSIG
20260209110543	DK6PX>APRS,TCPIP,qAC,T2CSNGRAD:;EDDK 201218z5051.85N/00708.27E^ EDDK 091050Z AUTO 13010KT 100V160 9999 FEW025 06/02 Q1007 NOSIG
20260209120543	DK6PX>APRS,TCPIP,qAC,T2DENMARK:;EDDK 201218z5051.85N/00708.27E^ EDDK 091150Z AUTO 14018KT 9999 BKN024 06/01 Q1006 NOSIG
20260209130543	DK6PX>APRS,TCPIP,qAC,T2POLNW:;EDDK 201218z5051.85N/00708.27E^ EDDK 091250Z AUTO 15015KT 9999 BKN024 06/01 Q1006 BECMG 13010KT
20260209140544	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;EDDK 201218z5051.85N/00708.27E^ EDDK 091350Z AUTO 15011KT 9999 BKN024 07/01 Q1006 NOSIG