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
20260117131726OK2ZAW-17>APLG0,qAO,OK0BAF-10:=501?.99GL01625.35E&LoRa sun HG
20260117133226OK2ZAW-17>APLG0,qAO,OK2AF-10:=5016.90NL016235ɂYF4CDiLʃ
20260117145726OK2ZAW-17>APLG0,qAO,OK2AF-10:=516.90NL01625.35E&LoRa sun DiGi
20260117150726OK2ZAW-17>APLG0,qAO,OK1BF-10:=501 2Lq225.35E[-u(DIG
20260117152228OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90NN3625.35E&LoRa sun DmiH
20260117171226OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.YV.L3<.3% ,4a%spn DiGi
20260117171226OK2ZAW-17>APLG0,qAS,OK1TPG-27:=506zP$;[f5B)st