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
20250913025535OK2ZAW-17>APLG0,qAO,OK0BAF-10:=5016.90NL0162%.35E&LoRa sun DiGi
20250913030535OK2ZAW-17>APLG0,qAO,OK1KKY-17:=5016.90H4q265.3?E&LoRa sun DiGk
20250913040535OK2ZAW-17>APLG0,qAO,OK1KKY-17:=5016.90)01V45.35E&LoRa sun DiGi
20250913042035OK2ZAW-17>APLG0,qAO,OK1KKY-17:=5016.90.L625.35E&LoRa sun DiGi
20250913043535OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90NL01625.35LoRm sun DiGi
20250913050035OK2ZAW-17>APLG0,qAO,OK1KKY-17:=5016.90NIe1c·µ.35EżE6[h sun DiGi
20250913060035OK2ZAW-17>APLG0,qAO,OK1KKY-17:=501.90NL01625.35E&LoRa sun DiGi
20250913061535OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90NL016<.3L&LoRa sun DiGi
20250913063035OK2ZAW-17>APLG0,qAO,OK2R-12:=501v*90NL01625.35E&LoRa sun DiGi
20250913063535OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90NLpq265.35/Ra sun DiGi
20250913065035OK2ZAW-17>AUIN0,qAO,OK2R-12:=501$)!VU605+c0E&LoRa sun DiGi
20250913065535OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90Lp0r7=qE,LoRk sunpD9l
20250913072035OK2ZAW-17>APLG0,qAO,OK0BAF-10:=50±6®±0FL01625.35E&LoRa sun DiGi
20250913072535OK2ZAW-17>APJG6,qAO,OK2R-12:=501 92Ituv65.35Eb /Ve sun DiGi
20250913073535OK2ZAW-17>APLG0,qAO,OK2R-12:=50!&/80O]3CM*LR8%vp>%UkDY
20250913080537OK2ZAW-17>APLG0,qAO,OK2R-12:=50593.,076217G@Qd sun DiGi