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
20240519040436OK2ZAW-17>APLG0,qAO,OK2CME-12:=501.90NL32!%>"%D&LoRa@u&DiGi
20240519041435OK2ZAW-17>APLG0,qAO,OK1MRM-22:=501610NL01624 P
20240519055435OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50pD(k-iK@dp
20240519060935OK2ZAW-17>APLG0,qAO,OK2ULQ-11:=506 0X#25.35E&LoRa sun DiGi
20240519063437OK2ZAW-17>APLG0,qAS,OK0BAF-10:=501 LL0165:5EFlk sun DGc
20240519065935OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL01625.35S3o[r>f
20240519070935OK2ZAW-17>APLG0,qAR,OK1JRA-2:=50"0BL016R5(S3C&LoRa sun DiGi
20240519074935OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL01625.35(/G~u!Z5