APRS Packet Errors for EDDF-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
20260208150534DK6PX>APRS,TCPIP*,qAC,T2CZECH:;EDDF-met *080219z5002.12N/00833.40E^ EDDF 081450Z AUTO 11003KT 090V150 9999 OVC018 07/03 Q1009 NOSIG
20260208160534DK6PX>APRS,TCPIP*,qAC,T2FRANCE:;EDDF-met *080219z5002.12N/00833.40E^ EDDF 081550Z AUTO 01005KT 9999 OVC017 07/04 Q1009 NOSIG
20260208170535DK6PX>APRS,TCPIP*,qAC,T2ROMANIA:;EDDF-met *080219z5002.12N/00833.40E^ EDDF 081650Z AUTO 02007KT 9999 BKN021 06/03 Q1009 NOSIG
20260208180534DK6PX>APRS,TCPIP*,qAC,T2DENMARK:;EDDF-met *080219z5002.12N/00833.40E^ EDDF 081750Z AUTO 08006KT 9999 FEW016 05/03 Q1009 NOSIG
20260208190534DK6PX>APRS,TCPIP*,qAC,T2ROMANIA:;EDDF-met *080219z5002.12N/00833.40E^ EDDF 081850Z AUTO 06005KT CAVOK 03/02 Q1010 BECMG 4000 BR
20260208200534DK6PX>APRS,TCPIP*,qAC,T2UKRAINE:;EDDF-met *080219z5002.12N/00833.40E^ EDDF 081950Z AUTO 04005KT 360V060 2400 0600 R07L/P2000N R07C/P2000N R07R/P2000N R18/1800D BCFG BKN001 02/02 Q1010 TEMPO 1200