APRS Packet Errors for YO5ZA-1 (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
20261101070043YO5ZA-1>APRS,WIDE2-1,qAR,SQ5BIH-1:!0000.00N/00000.00W>890 56 58 272 41 m317 M119 r250
20261101070139YO5ZA-1>APRS,WIDE2-1,qAR,SQ5BIH-1:!0000.00N/00000.00W>889 58 60 283 41 m317 M118 r250
20261101071440YO5ZA-1>APRS,WIDE2-1,qAR,SQ5BIH-1:!0000.00N/00000.00W>857 67 51 295 41 m317 M118 r250
20261101072733YO5ZA-1>APRS,WIDE2-1,qAR,SQ5BIH-1:!0000.00N/00000.00W>620 67 46 297 41 m317 M118 r250
20261101074410YO5ZA-1>APRS,WIDE2-1,qAR,SQ5BIH-1:!0000.00N/00000.00W>852 69 38 304 41 m317 M118 r250
20261101075706YO5ZA-1>APRS,WIDE2-1,qAR,SQ5BIH-1:!0000.00N/00000.00W>858 73 33 309 41 m317 M118 r250
20261101081003YO5ZA-1>APRS,WIDE2-1,qAR,SQ5BIH-1:!0000.00N/00000.00W>848 70 33 306 41 m317 M118 r250
20261101082645YO5ZA-1>APRS,WIDE2-1,qAR,SQ5BIH-1:!0000.00N/00000.00W>838 73 34 299 41 a0 d0 h6