APRS Packet Errors for YO5ZV (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
20261011124430YO5ZV>APRS,SV3GCB-10,WIDE2*,qAR,SV3GCB-3:!0000.00N/00000.00W>456 75 36 311 42 a0 d0 h16
20261011125658YO5ZV>APRS,SV3GCB-10,WIDE2*,qAR,SV3GCB-3:!0000.00N/00000.00W>439 74 29 314 42 m320 M124 r65
20261011130925YO5ZV>APRS,WIDE2-1,qAR,SV3GCB-3:!0000.00N/00000.00W>441 80 30 311 42 a2 d1 h16
20261011132752YO5ZV>APRS,WIDE2-1,qAR,SV3GCB-3:!0000.00N/00000.00W>454 79 31 310 42 m320 M124 r66
20261011134022YO5ZV>APRS,YM4KGT,WIDE2*,qAR,TA2BU-10:!0000.00N/00000.00W>468 76 28 316 42 m320 M124 r66
20261011135248YO5ZV>APRS,WIDE2-1,qAR,SV3GCB-3:!0000.00N/00000.00W>501 76 28 316 42 a2 d0 h16
20261011141116YO5ZV>APRS,YM3KZD*,qAR,YM1KTC-11:!0000.00N/00000.00W>479 78 34 309 42 m320 M124 r67
20261011142345YO5ZV>APRS,YM3KZD*,qAR,YM1KTC-11:!0000.00N/00000.00W>477 74 33 312 42 m320 M124 r67
20261011145436YO5ZV>APRS,WIDE2-1,qAR,SV5DDT-10:!0000.00N/00000.00W>525 72 39 306 42 m320 M125 r68
20261011150701YO5ZV>APRS,WIDE2-1,qAR,SV5DDT-10:!0000.00N/00000.00W>519 68 33 311 42 m320 M125 r68
20261011151922YO5ZV>APRS,WIDE2-1,qAR,SV5DDT-10:!0000.00N/00000.00W>517 66 41 206 42 a2 d1 h17