APRS Packet Errors for YO5ZI-7 (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
20260928145105YO5ZI-7>APRS,WIDE2-1,qAR,TA1MA:!0000.00N/00000.00W>635 76 20 320 42 m317 M126 r250
20260928145626YO5ZI-7>APRS,WIDE2-1,qAR,TA1MA:!0000.00N/00000.00W>619 73 22 319 42 m317 M126 r250
20260928145704YO5ZI-7>APRS,YM1KM-3,WIDE2*,qAR,TA0C-10:!0000.00N/00000.00W>619 73 22 319 42 m317 M126 r250
20260928150850YO5ZI-7>APRS,WIDE2-1,qAR,TA1MA:!0000.00N/00000.00W>323 73 20 319 42 a1 d0 h26
20260928152113YO5ZI-7>APRS,YM2ANK,WIDE2*,qAR,TA2VIP-1:!0000.00N/00000.00W>597 70 23 311 42 a2 d1 h26
20260928152636YO5ZI-7>APRS,WIDE2-1,qAR,TA1MA:!0000.00N/00000.00W>602 70 24 311 42 a0 d0 h26
20260928152710YO5ZI-7>APRS,YM1KM-3,WIDE2*,qAR,TA0C-10:!0000.00N/00000.00W>602 70 24 311 42 a0 d0 h26
20260928153854YO5ZI-7>APRS,WIDE2-1,qAR,YM2VTC:!0000.00N/00000.00W>579 63 20 322 42 a1 d0 h26
20260928155106YO5ZI-7>APRS,WIDE2-1,qAR,TA0C-10:!0000.00N/00000.00W>604 50 26 248 42 a2 d0 h27
20260928155640YO5ZI-7>APRS,WIDE2-1,qAR,TA0C-10:!0000.00N/00000.00W>591 45 51 0 42 a0 d0 h27