APRS Packet Errors for YO5ZI-9 (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
20260922164621YO5ZI-9>APRS,WIDE2-1,qAR,F5ZZ-10:!0000.00N/00000.00W>433 80 7 319 42 m322 M124 r20
20260922165913YO5ZI-9>APRS,WIDE2-1,qAR,F6ZAF:!0000.00N/00000.00W>439 73 10 321 42 m322 M124 r20
20260922170351YO5ZI-9>APRS,WIDE2-1,qAO,EB2BRA-10:!0000.00N/00000.00W>432 75 11 321 42 m322 M124 r21
20260922171641YO5ZI-9>APRS,WIDE2-1,qAR,F4BQH-13:!0000.00N/00000.00W>430 72 7 319 42 a1 d0 h5
20260922172930YO5ZI-9>APRS,WIDE2-1,qAR,F5ZZ-10:!0000.00N/00000.00W>415 66 10 133 42 m322 M124 r21
20260922173017YO5ZI-9>APRS,F6KPC-3,WIDE2*,qAR,F1ZIA:!0000.00N/00000.00W>415 66 10 133 42 m322 M124 r21
20260922173412YO5ZI-9>APRS,WIDE2-1,qAR,F5ZZ-10:!0000.00N/00000.00W>411 64 15 319 42 m322 M124 r22
20260922174657YO5ZI-9>APRS,WIDE2-1,qAR,F5ZZ-10:!0000.00N/00000.00W>343 67 11 232 42 a1 d0 h5
20260922175939YO5ZI-9>APRS,WIDE2-1,qAR,F5ZZ-10:!0000.00N/00000.00W>392 56 15 72 42 m322 M124 r22
20260922180428YO5ZI-9>APRS,WIDE2-1,qAR,F5ZZ-10:!0000.00N/00000.00W>375 48 37 0 42 m322 M123 r23