APRS Packet Errors for YO5ZA-12 (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
20260402195935YO5ZA-12>APRS,W7PND-3,WIDE2*,qAR,N7RRB-3:!0000.00N/00000.00W>778 90 -60 405 42
20260402201246YO5ZA-12>APRS,WIDE2-1,qAR,N0NPO-2:!0000.00N/00000.00W>726 94 -62 404 42
20260402203356YO5ZA-12>APRS,WIDE2-1,qAR,N0NPO-2:!0000.00N/00000.00W>898 90 -67 413 42
20260402205226YO5ZA-12>APRS,WIDE2-1,qAR,N0NPO-2:!0000.00N/00000.00W>739 95 -60 403 42
20260402211338YO5ZA-12>APRS,WIDE2-1,qAR,N0NPO-2:!0000.00N/00000.00W>873 96 -48 390 42
20260402213449YO5ZA-12>APRS,WIDE2-1,qAO,KC0CAU-10:!0000.00N/00000.00W>777 317 253 -62 1309 0 42
20260402215559YO5ZA-12>APRS,WIDE2-1,qAR,N0NPO-2:!0000.00N/00000.00W>174 81 -17 359 43
20260402221149YO5ZA-12>APRS,WIDE2-1,qAR,N0NPO-2:!0000.00N/00000.00W>596 96 -29 366 42
20260402223924YO5ZA-12>APRS,WIDE2-1,qAO,KC0CAU-10:!0000.00N/00000.00W>139 82 -5 343 43