APRS Packet Errors for YO5ZX-2 (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
20260615063119YO5ZX-2>APRS,WIDE2-1,qAR,SV1AMY-3:!0000.00N/00000.00W>528 82 30 317 43
20260615064125YO5ZX-2>APRS,WIDE2-1,qAR,YM1KTC-11:!0000.00N/00000.00W>486 77 29 317 43
20260615072229YO5ZX-2>APRS,TA3F-14*,qAR,TB3ACE-10:!0000.00N/00000.00W>567 76 31 316 43
20260615073232YO5ZX-2>APRS,WIDE2-1,qAR,YM1KTC-11:!0000.00N/00000.00W>543 77 30 320 43
20260615075407YO5ZX-2>APRS,WIDE2-1,qAR,YM1KTC-11:!0000.00N/00000.00W>485 69 32 315 43 m321 M135 r250
20260615075428YO5ZX-2>APRS,WIDE2-1,qAR,SV1AMY-3:!0000.00N/00000.00W>486 70 32 320 43
20260615085459YO5ZX-2>APRS,WIDE2-1,qAR,SV1AMY-3:!0000.00N/00000.00W>496 71 30 322 43
20260615090504YO5ZX-2>APRS,WIDE2-1,qAR,SV5DDT-10:!0000.00N/00000.00W>481 68 30 322 43
20260615095551YO5ZX-2>APRS,WIDE2-1,qAR,YM1KTC-11:!0000.00N/00000.00W>491 67 31 316 43
20260615100556YO5ZX-2>APRS,WIDE2-1,qAO,YM5SKE-10:!0000.00N/00000.00W>470 69 31 315 43
20260615110627YO5ZX-2>APRS,WIDE2-1,qAO,YM5SKE-10:!0000.00N/00000.00W>436 72 30 320 43 a55 d0 h32
20260615111632YO5ZX-2>APRS,WIDE2-1,qAO,YM5SKE-10:!0000.00N/00000.00W>439 75 28 322 43