APRS Packet Errors for EDDR (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
20260208150538	DK6PX>APRS,TCPIP,qAC,T2CZECH:;EDDR 201218z4913.13N/00706.72E^ EDDR 081450Z AUTO 04009KT 9999 BKN007 06/04 Q1007 NOSIG
20260208160554	DK6PX>APRS,TCPIP,qAC,T2FRANCE:;EDDR 201218z4913.13N/00706.72E^ EDDR 081550Z AUTO 05011KT 9999 BKN006 05/04 Q1007 NOSIG
20260208170538	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;EDDR 201218z4913.13N/00706.72E^ EDDR 081650Z AUTO 05010KT 9999 BKN005 04/03 Q1007 NOSIG
20260208180537	DK6PX>APRS,TCPIP,qAC,T2DENMARK:;EDDR 201218z4913.13N/00706.72E^ EDDR 081750Z AUTO 06009KT 030V100 9999 OVC004 04/03 Q1008 NOSIG
20260208190538	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;EDDR 201218z4913.13N/00706.72E^ EDDR 081850Z AUTO 08009KT 050V110 9999 OVC003 03/02 Q1008 NOSIG
20260208200608	DK6PX>APRS,TCPIP,qAC,T2UKRAINE:;EDDR 201218z4913.13N/00706.72E^ EDDR 081950Z AUTO 06010KT 9999 OVC007 03/02 Q1008 NOSIG