APRS Packet Errors for YO5ZY (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
20260318205127YO5ZY>APRS,XE1CGG-1,WIDE2*,qAR,XE1IFV-2:!0000.00N/00000.00W>661 73 -25 368 44
20260318211629YO5ZY>APRS,WIDE2-1,qAR,XE1N-10:!0000.00N/00000.00W>608 83 -29 372 44
20260318214137YO5ZY>APRS,WIDE2-1,qAR,XE1N-10:!0000.00N/00000.00W>629 78 -20 363 44
20260318220642YO5ZY>APRS,WIDE2-1,qAR,XE1N-10:!0000.00N/00000.00W>637 317 449 -33 1464 0 44
20260318222859YO5ZY>APRS,WIDE2-1,qAR,XE1N-10:!0000.00N/00000.00W>568 87 -22 362 44
20260318225112YO5ZY>APRS,WIDE2-1,qAR,XE1N-10:!0000.00N/00000.00W>562 75 -25 366 44
20260318231325YO5ZY>APRS,WIDE2-1,qAR,XE1CKJ-1:!0000.00N/00000.00W>644 76 -28 373 44
20260318233830YO5ZY>APRS,WIDE2-1,qAR,XE1IFV-2:!0000.00N/00000.00W>603 83 -23 368 44
20260319000334YO5ZY>APRS,WIDE2-1,qAR,XE1IFV-2:!0000.00N/00000.00W>670 74 -21 360 44
20260319002048YO5ZY>APRS,WIDE2-1,qAR,XE1N-10:!0000.00N/00000.00W>687 317 451 -21 1464 0 44