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
20260220065740	YO5ZV>APRS,WIDE2-1,qAR,IZ0PMP-1:!0000.00N/00000.00W>661 66 60 282 43 a1 d0 355
20260220073508	YO5ZV>APRS,WIDE2-1,qAR,IZ0PMP-1:!0000.00N/00000.00W>715 77 13 326 43 a2 d1 356
20260220081600	YO5ZV>APRS,WIDE2-1,qAR,IU0JIW-1:!0000.00N/00000.00W>665 84 -14 305 43 a6 d0 356
20260220081900	YO5ZV>APRS,WIDE2-1,qAR,IS0ANU-12:!0000.00N/00000.00W>715 77 -17 358 43 a7 d0 356
20260220084051	YO5ZV>APRS,WIDE2-1,qAR,IU0JIW-1:!0000.00N/00000.00W>763 314 357 -27 1373 0 43
20260220084350	YO5ZV>APRS,WIDE2-1,qAR,IS0ANU-12:!0000.00N/00000.00W>561 68 -36 377 43
20260220090342	YO5ZV>APRS,WIDE2-1,qAR,IU0JIW-1:!0000.00N/00000.00W>492 88 -13 351 43
20260220090403	YO5ZV>APRS,WIDE2-1,qAR,IZ0PMP-1:!0000.00N/00000.00W>530 89 -5 342 43
20260220092352	YO5ZV>APRS,WIDE2-1,qAR,IU0JIW-1:!0000.00N/00000.00W>573 81 -26 362 43
20260220092651	YO5ZV>APRS,WIDE2-1,qAR,IZ0PMP-1:!0000.00N/00000.00W>488 81 -33 375 43
20260220100538	YO5ZV>APRS,WIDE2-1,qAR,IZ0PMP-1:!0000.00N/00000.00W>572 90 -13 349 43
20260220100838	YO5ZV>APRS,WIDE2-1,qAR,IZ0PMP-1:!0000.00N/00000.00W>570 82 -27 369 43