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
20251219194244OK2ZAW-17>APLG0,qAO,OK0BAF-10:=5016.90^!w3t9C&HgRw᥵ѯ
20251219194244OK2ZAW-17>APLG0,qAO,OK2R-12:=5016>81nNY#9GoRwfҭ
20251219195745OK2ZAW-17>APLG0,qAO,OK2R-12:=5016+<5KL01625.35E&LoRa sun DiGi
20251219201244OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90L016j`ceGLOBD3O
20251219204244OK2ZAW-17>APLG0,qAO,OK2R-12:=50&ڙ6,&3%E&LoR)b DiGi
20251219205747OK2ZAW-17>APLG0,qAO,OK0BAF-10:=50Qk3;6;&?9E.@dAu;
20251219214744OK2ZAW-17>APLG0,qAO,OK0BAF-10:=5016.90N,6Q605.35E 41s7}}`bX
20251219220244OK2ZAW-17>APLG0,qAO,OK2R-12:=50. GL056i30@ǀx
20251219221244OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90.*0W045.35E&Lo[a sun DiGi
20251219223244OK2ZAW-17>APLG,qAO,OK2R-12:==09 #605.35EvOlRd sun DiGi
20251219232244OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90NL01625.35 NO11tS~P:
20251220002244OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90NL01v>5.35E&LoRa sun DiGi
20251220003244OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90NL0165"@oR({f DiGi
20251220005744OK2ZAW-17>APIG0,qAO,OK2R-12:=5016.90NL01625.35 Xg|Ge
20251220010244OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90NL0162<.5E&LoRa sun DiGi