APRS Packet Errors for OK2ZAW-17 (last 24 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
20250508080604OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90N̰,$A.B+Pk/t-
20250508081604OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50.$*01T4u.w5EfkAq wjGZ
20250508082604OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5015 3ML01625.35E&LoRa sun qYDi
20250508084604OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5018NL016?340il sun@o-o
20250508091604OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90^25.35Xa0sun"DiGi
20250508094604OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.0N̰625.35&oR{
20250508100104OK2ZAW-17>APLG0,qAS,OL7M-10:=5016.90NL016R5N35C&LoRa rto!D
20250508125604OK2ZAW-17>APLG0,qAO,OK1KKY-17:=5016.90ND01:_,2¨M_&m9%{
20250508130605OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90N|"1$52uL^hs%n&Di!o
20250508131604OK2ZAW-17>APLG0,qAO,OK1KKY-17:=501p*> E,,+cxE(|| Y
20250508132104OK2ZAW-17>APLG0,qAO,OK1KKY-17:=5016.90N mhw3
20250508164604OK2ZAW-17>APLG0,qAO,OK1KKY-17:=501@n FB(/vAr
20250509011104OK2ZAW-17>APLG0,qAS,OK1TPG-27:=508 SNR=-21dB RSSI=-77db
20250509011604OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL`af75.35E#oRd sun@"Ao
20250509053104OK2ZAW-17>APLG0,qAO,OK2R-12:=501- 0ML01625.35E&LoRa sun DiGi