APRS Packet Errors for YO5ZP-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
20260402190921	YO5ZP-6>APRS,WIDE2-1,qAR,XE2JA-10:!0000.00N/00000.00W>734 314 634 -66 1466 0 44
20260402202327	YO5ZP-6>APRS,WIDE2-1,qAR,XE2JA-10:!0000.00N/00000.00W>693 76 -53 396 44
20260402204422	YO5ZP-6>APRS,WIDE2-1,qAR,XE2JA-10:!0000.00N/00000.00W>739 71 -54 398 44
20260402210517	YO5ZP-6>APRS,WIDE2-1,qAR,XE2JA-10:!0000.00N/00000.00W>689 81 -62 403 44
20260402212613	YO5ZP-6>APRS,WIDE2-1,qAR,XE2JA-10:!0000.00N/00000.00W>767 75 -64 405 44
20260402215735	YO5ZP-6>APRS,WIDE2-1,qAR,XE2JA-10:!0000.00N/00000.00W>752 82 -15 356 44
20260402221909	YO5ZP-6>APRS,WIDE2-1,qAR,XE2JA-10:!0000.00N/00000.00W>782 78 -34 373 44
20260402224006	YO5ZP-6>APRS,WIDE2-1,qAR,XE2JA-10:!0000.00N/00000.00W>690 88 -48 389 44
20260402230140	YO5ZP-6>APRS,WIDE2-1,qAR,XE2JA-10:!0000.00N/00000.00W>804 76 -37 374 44