APRS Packet Errors for YO5ZP-3 (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
20251123015415YO5ZP-3>APRS,BI4NQQ-10*,WIDE2,qAO,BI4NQQ-10:!0000.00N/00000.00W>363 74 37 314 42
20251123020155YO5ZP-3>APRS,WIDE2-1,qAO,BI4NQD-10:!0000.00N/00000.00W>363 74 37 314 42
20251123023930YO5ZP-3>APRS,BI4NQQ-10*,WIDE2,qAO,BI4NQQ-10:!0000.00N/00000.00W>361 77 37 1236 77 42 240
20251123055500YO5ZP-3>APRS,WIDE2-1,qAR,JA5HWI-10:!0000.00N/00000.00W>294 74 37 310 42
20251123061429YO5ZP-3>APRS,WIDE2-1,qAR,JH4KWH-10:!0000.00N/00000.00W>257 80 37 1235 80 42 240