APRS Packet Errors for EDDC-met (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
20260208180539DK6PX>APRS,TCPIP*,qAC,T2DENMARK:;EDDC-met *201218z5107.73N/01345.81E^ EDDC 081750Z AUTO 04005KT 2700 BR OVC002 00/00 Q1011 NOSIG
20260208190540DK6PX>APRS,TCPIP*,qAC,T2ROMANIA:;EDDC-met *201218z5107.73N/01345.81E^ EDDC 081850Z AUTO 06006KT 1100 0900 R22/1500D BCFG OVC001 00/00 Q1011 TEMPO 0700 FZFG
20260208200610DK6PX>APRS,TCPIP*,qAC,T2UKRAINE:;EDDC-met *201218z5107.73N/01345.81E^ EDDC 081950Z AUTO 06006KT 0900 0800 R22/1100N FG OVC001 00/00 Q1011
20260208210540DK6PX>APRS,TCPIP*,qAC,T2ERFURT:;EDDC-met *201218z5107.73N/01345.81E^ EDDC 082050Z AUTO 07006KT 1900 BR OVC001 00/M00 Q1011 TEMPO 0500 FG
20260208220555DK6PX>APRS,TCPIP*,qAC,T2DENMARK:;EDDC-met *201218z5107.73N/01345.81E^ EDDC 082150Z AUTO 07007KT 2800 1200 R22/P2000N BR OVC002 00/M00 Q1011 TEMPO 0700 FG
20260208230540DK6PX>APRS,TCPIP*,qAC,T2CZECH:;EDDC-met *201218z5107.73N/01345.81E^ EDDC 082250Z AUTO 07005KT 4700 BR BKN003 OVC017 M00/M00 Q1011