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
20260209110534DK6PX>APRS,TCPIP*,qAC,T2CSNGRAD:;EDDF-met *080219z5002.12N/00833.40E^ EDDF 091050Z AUTO 08005KT 360V130 9999 BKN012 OVC028 05/02 Q1008 BECMG BKN015
20260209120534DK6PX>APRS,TCPIP*,qAC,T2DENMARK:;EDDF-met *080219z5002.12N/00833.40E^ EDDF 091150Z AUTO 12007KT 080V150 9999 BKN014 OVC027 05/02 Q1008 BECMG BKN015
20260209130534DK6PX>APRS,TCPIP*,qAC,T2POLNW:;EDDF-met *080219z5002.12N/00833.40E^ EDDF 091250Z AUTO 10006KT 9999 BKN015 OVC027 05/02 Q1007 NOSIG
20260209140535DK6PX>APRS,TCPIP*,qAC,T2ROMANIA:;EDDF-met *080219z5002.12N/00833.40E^ EDDF 091350Z AUTO 10004KT 050V160 9999 BKN019 OVC023 06/02 Q1007 NOSIG
20260209150534DK6PX>APRS,TCPIP*,qAC,T2FINLAND:;EDDF-met *080219z5002.12N/00833.40E^ EDDF 091450Z AUTO 14005KT 9999 BKN018 06/02 Q1007 NOSIG
20260209160534DK6PX>APRS,TCPIP*,qAC,T2CSNGRAD:;EDDF-met *080219z5002.12N/00833.40E^ EDDF 091550Z AUTO 15004KT 110V240 9999 OVC022 06/01 Q1007 NOSIG