APRS Packet Errors for YO5ZA-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
20251214092046YO5ZA-12>APRS,WIDE2-1,qAR,LZ0BGY:!0000.00N/00000.00W>824 81 20 323 42
20251214093104YO5ZA-12>APRS,WIDE2-1,qAR,YO7JYL-10:!0000.00N/00000.00W>659 97 22 319 41
20251214102341YO5ZA-12>APRS,WIDE2-1,qAR,YO3KXL-10:!0000.00N/00000.00W>686 91 20 322 42
20251214103039YO5ZA-12>APRS,WIDE2-1,qAR,YO3KXL-10:!0000.00N/00000.00W>791 84 20 315 42
20251214112905YO5ZA-12>APRS,WIDE2-1,qAR,LZ0BGY:!0000.00N/00000.00W>787 83 20 318 42
20251214113922YO5ZA-12>APRS,WIDE2-1,qAR,LZ2AB:!0000.00N/00000.00W>788 81 18 326 42
20251214124101YO5ZA-12>APRS,WIDE2-1,qAR,LZ0BGY:!0000.00N/00000.00W>790 84 20 314 42
20251214125117YO5ZA-12>APRS,WIDE2-1,qAR,LZ0BGY:!0000.00N/00000.00W>774 79 20 320 42