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
20250625093551OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL016²5.³5EOa¢ ¿¹n DiGi
20250625095553OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL0162<.35E ?bg sun DiGi
20250625100051OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL01625.35&Loa sun DiGi
20250625100551OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50!&.) NL016R3.USC&LoRa sun DiGi
20250625101051OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL01625.35&IjRa sun T{Fi
20250625102551OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL0162=16&Ioa sun DiGi
20250625103551OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL0162<¾:¥E&LoRa sun DiGi
20250625104551OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50¡6·00GFü=0$%>"$ä&LÏXk sun DiGi
20250625105551OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL016²=.35Ū
20250625113051OK2ZAW-17>APLG0,qAS,OK1TPG-27:=516.90NL01625.35E&LoRa sun DiGi
20250625123550OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50!> !MLT15.35Å&DoRá({un DiÇi*
20250625134551OK2ZAW-17>APLG0,qAO,OK2R-12:=5016+9`KO01525.35E&LoRa sun DiGi