APRS Packet Errors for LOWK (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
20260208150708	DK6PX>APRS,TCPIP,qAC,T2CZECH:;LOWK 010113z4639.00N/01419.39E^ LOWK 081450Z 03002KT 9999 FEW007 BKN009 03/01 Q1008 NOSIG
20260208160724	DK6PX>APRS,TCPIP,qAC,T2FRANCE:;LOWK 010113z4639.00N/01419.39E^ LOWK 081550Z 07004KT 9999 FEW007 BKN009 03/01 Q1008 NOSIG
20260208170756	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;LOWK 010113z4639.00N/01419.39E^ LOWK 081650Z 09004KT 9999 BKN008 03/01 Q1008 NOSIG
20260208180659	DK6PX>APRS,TCPIP,qAC,T2DENMARK:;LOWK 010113z4639.00N/01419.39E^ LOWK 081750Z AUTO 09003KT 9999 FEW005 BKN007 03/01 Q1009 NOSIG
20260208190703	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;LOWK 010113z4639.00N/01419.39E^ LOWK 081850Z AUTO VRB01KT 9999 FEW005 BKN006 03/01 Q1009 TEMPO FM1930 4000 BR BKN004
20260208200738	DK6PX>APRS,TCPIP,qAC,T2UKRAINE:;LOWK 010113z4639.00N/01419.39E^ LOWK 081950Z AUTO VRB02KT 9999 SCT005 BKN006 03/01 Q1009 TEMPO BKN004