APRS Packet Errors for OK2ZAW-17 (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
20251215200746OK2ZAW-17>APLG0,qAS,OE3XRC-12:=5016.90NL016"5.3%E&LoRa sun DiGi
20251215200746OK2ZAW-17>aRlg0,qAO,OM3KUK-10:=50±6.98fn!25.355 :
20251215201746OK2ZAW-17>APLG0,qAO,OE5XIM-11:=5016.90#GV3f@&LoRa sun DiGi
20251215212753OK2ZAW-17>APLG0,qAO,OE5XIM-11:=5016.903V(`cE&LoRa sun DiGi
20251215213252OK2ZAW-17>APLG0,qAO,OE5XGL-11:=50190DL00&2;5@dsufU
20251215213751OK2ZAW-17>APLG0,qAO,OE5XIM-11:=50f.90NL01625.35E&LoRa sun DiGi
20251215214750OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90NL0162#
20251215223746OK2ZAW-17>APLG0,qAO,OE5XOL-11:=5016.90NLP1625.35E&LoRa sun DiGi
20251215223746OK2ZAW-17>APLG0,qAO,OK2AF-10:=5016n90NL01625.35E&LoRa sun DiGi
20251215231746OK2ZAW-17>APLG0,qAS,OE3XRC-12:=5016.90NL01624>35E7]nC` {ynàD¥GiF
20251215231748OK2ZAW-17>APLG0,qAS,OE3XRC-11:=50±ú¢»0|„zŸe f<ÅuUkeêil²uXFHð
20251215234748OK2ZAW-17>HPEG9,qAO,OE3YHC-11:=501.2NL01625.35E&LoRa sun DiGi:
20251216000248OK2ZAW-17>APLG0,qAO,OK1BF-10:=50!&.8 N1egeN6Es|
20251216002249OK2ZAW-17>APLG0,qAO,OE5XGL-11:=5016.90NL5df7.35E&LoRa sun DiGi
20251216005246OK2ZAW-17>APLG0,qAO,OM3KUK-10:=5016.90NL016"%."%D&LoRa sun DiGI
20251216012246OK2ZAW-17>APLG0,qAO,OE5XGL-11:=5016.90NL01625*sqEEfXad75nA
20251216012746OK2ZAW-17>APLG6,qAS,OE3XRC-12:=501.92\0 63½®»=Mæ@£Ra sun DiGi