APRS Packet Errors for ELLX (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
20260209120618	DK6PX>APRS,TCPIP,qAC,T2DENMARK:;ELLX 201218z4938.07N/00613.27E^ ELLX 091150Z 16007KT 8000 BKN005 02/01 Q1005 NOSIG
20260209130621	DK6PX>APRS,TCPIP,qAC,T2POLNW:;ELLX 201218z4938.07N/00613.27E^ ELLX 091250Z 17006KT 1500 BR BKN003 02/02 Q1005 NOSIG
20260209140629	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;ELLX 201218z4938.07N/00613.27E^ ELLX 091350Z 15006KT 120V180 1200 R24/P2000N BR OVC002 02/02 Q1004 TEMPO 0800 FG BKN002
20260209150634	DK6PX>APRS,TCPIP,qAC,T2FINLAND:;ELLX 201218z4938.07N/00613.27E^ ELLX 091450Z 14005KT 110V170 1500 BR OVC002 02/02 Q1004 TEMPO 0800 FG
20260209160705	DK6PX>APRS,TCPIP,qAC,T2CSNGRAD:;ELLX 201218z4938.07N/00613.27E^ ELLX 091550Z 15005KT 110V190 0500 R24/1300VP2000D FG OVC001 02/02 Q1004 TEMPO 1200 BR
20260209170618	DK6PX>APRS,TCPIP,qAC,T2SWEDEN:;ELLX 201218z4938.07N/00613.27E^ ELLX 091650Z 13006KT 100V160 0300 R24/1500N FG OVC001 02/02 Q1003 BECMG 0200