APRS Packet Errors for YO5ZG-12 (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
20251215123804YO5ZG-12>APRS,WIDE2-1,qAR,IZ0RIN-1:!0000.00N/00000.00W>384 79 -2 349 41
20251215124201YO5ZG-12>APRS,WIDE2-1,qAR,IU0JIW-1:!0000.00N/00000.00W>352 78 -8 349 41
20251215130545YO5ZG-12>APRS,WIDE2-1,qAR,IU0ESP-4:!0000.00N/00000.00W>386 71 -2 349 41
20251215130942YO5ZG-12>APRS,IH9GUB-13*,qAO,IW9GTD-10:!0000.00N/00000.00W>375 70 -6 352 41
20251215134415YO5ZG-12>APRS,WIDE2-1,qAR,IR0AAL-10:!0000.00N/00000.00W>319 65 -3 345 41
20251215135151YO5ZG-12>APRS,WIDE2-1,qAO,IZ0ORT-1:!0000.00N/00000.00W>331 67 -4 350 41
20251215144121YO5ZG-12>APRS,WIDE2-1,qAR,IR0AAL-10:!0000.00N/00000.00W>390 318 31 3 1142 0 41 25
20251215145240YO5ZG-12>APRS,WIDE2-1,qAR,IU8MFH-1:!0000.00N/00000.00W>381 61 4 338 41