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
20260208150543	DK6PX>APRS,TCPIP,qAC,T2CZECH:;EDDK 201218z5051.85N/00708.27E^ EDDK 081450Z AUTO 11006KT 070V160 9999 OVC011 06/03 Q1009 BECMG SCT015
20260208160614	DK6PX>APRS,TCPIP,qAC,T2FRANCE:;EDDK 201218z5051.85N/00708.27E^ EDDK 081550Z AUTO 13006KT 090V160 9999 BKN011 05/03 Q1009 BECMG SCT015
20260208170544	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;EDDK 201218z5051.85N/00708.27E^ EDDK 081650Z AUTO 12004KT CAVOK 04/03 Q1009 NOSIG
20260208180543	DK6PX>APRS,TCPIP,qAC,T2DENMARK:;EDDK 201218z5051.85N/00708.27E^ EDDK 081750Z AUTO 12005KT 090V150 CAVOK 04/02 Q1009 NOSIG
20260208190543	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;EDDK 201218z5051.85N/00708.27E^ EDDK 081850Z AUTO 10005KT 070V140 CAVOK 03/02 Q1009 NOSIG
20260208200614	DK6PX>APRS,TCPIP,qAC,T2UKRAINE:;EDDK 201218z5051.85N/00708.27E^ EDDK 081950Z AUTO 08004KT CAVOK 03/01 Q1009 NOSIG