APRS Packet Errors for YO5ZX-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
20260417034148YO5ZX-12>APRS,WIDE2-1,qAR,R2BBS-4:!0000.00N/00000.00W>814 66 27 313 42 a6 d1 80
20260417044824YO5ZX-12>APRS,WIDE2-1,qAR,R2BBS-4:!0000.00N/00000.00W>815 317 81 26 1283 0 42 2
20260417045922YO5ZX-12>APRS,WIDE2-1,qAR,R2BBS-4:!0000.00N/00000.00W>823 81 24 316 42
20260417060605YO5ZX-12>APRS,WIDE2-1,qAR,UB1QBQ-1:!0000.00N/00000.00W>884 82 25 317 42
20260417061708YO5ZX-12>APRS,WIDE2-1,qAR,UB1QBQ-1:!0000.00N/00000.00W>873 86 24 318 42