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
20260208150634	DK6PX>APRS,TCPIP,qAC,T2CZECH:;ELLX 201218z4938.07N/00613.27E^ ELLX 081450Z 07007KT 2000 1200SE R24/P2000N BR OVC001 04/04 Q1007 TEMPO 1500 BR
20260208160634	DK6PX>APRS,TCPIP,qAC,T2FRANCE:;ELLX 201218z4938.07N/00613.27E^ ELLX 081550Z 06007KT 4500 BR OVC001 04/04 Q1007 NOSIG
20260208170651	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;ELLX 201218z4938.07N/00613.27E^ ELLX 081650Z 06007KT 9999 FEW006 BKN008 04/04 Q1007 NOSIG
20260208180609	DK6PX>APRS,TCPIP,qAC,T2DENMARK:;ELLX 201218z4938.07N/00613.27E^ ELLX 081750Z 07007KT 9999 FEW006 OVC008 05/04 Q1007 NOSIG
20260208190629	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;ELLX 201218z4938.07N/00613.27E^ ELLX 081850Z 07009KT 9999 OVC006 04/03 Q1007 NOSIG
20260208200656	DK6PX>APRS,TCPIP,qAC,T2UKRAINE:;ELLX 201218z4938.07N/00613.27E^ ELLX 081950Z 07005KT 9999 OVC004 04/03 Q1008 NOSIG