APRS Packet Errors for YO5ZR-6 (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
20261011123318YO5ZR-6>APRS,SV3GCB-10,WIDE2*,qAR,SV3GCB-3:!0000.00N/00000.00W>439 66 30 315 42 m320 M124 r66
20261011124556YO5ZR-6>APRS,SV3GCB-10,WIDE2*,qAR,SV3GCB-3:!0000.00N/00000.00W>425 67 34 314 42 m320 M124 r66
20261011130259YO5ZR-6>APRS,YM4KGT,WIDE2*,qAR,TA2BU-10:!0000.00N/00000.00W>422 76 35 310 42 a0 d0 h16
20261011131540YO5ZR-6>APRS,SV3GCB-11,WIDE2*,qAR,SV3GCB-3:!0000.00N/00000.00W>433 70 30 316 42 a1 d0 h16
20261011132818YO5ZR-6>APRS,SV3GCB-10,WIDE2*,qAR,SV3GCB-3:!0000.00N/00000.00W>427 67 33 317 42 m320 M124 r67
20261011134518YO5ZR-6>APRS,SV3GCB-11,WIDE2*,qAR,SV3GCB-3:!0000.00N/00000.00W>465 77 38 309 42 m320 M124 r68
20261011135756YO5ZR-6>APRS,SV3GCB-10,WIDE2*,qAR,SV3GCB-3:!0000.00N/00000.00W>457 74 32 312 42 a1 d0 h16
20261011141036YO5ZR-6>APRS,SV3GCB-10,WIDE2*,qAR,SV3GCB-3:!0000.00N/00000.00W>457 76 33 312 42 a2 d1 h17
20261011142735YO5ZR-6>APRS,YM4KGT,WIDE2*,qAR,TA2BU-10:!0000.00N/00000.00W>232 79 43 303 41 m320 M124 r69
20261011143605YO5ZR-6>APRS,WIDE2-1,qAR,5B4CY-1:!0000.00N/00000.00W>454 67 36 304 42 m320 M124 r69
20261011152230YO5ZR-6>APRS,SV3GCB-11,WIDE2*,qAR,SV3GCB-3:!0000.00N/00000.00W>457 59 34 312 42 a1 d0 h17