APRS Packet Errors for YO5ZF-2 (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
20251226184305YO5ZF-2>APRS,WIDE2-1,qAR,DRMT39:!0000.00N/00000.00W>260 320 42 34 1229 0 42 2 a11 d3 42
20251226195935YO5ZF-2>APRS,WIDE2-1,qAR,VE7CHW:!0000.00N/00000.00W>251 84 23 316 42
20251226212831YO5ZF-2>APRS,WIDE2-1,qAO,VA7AV-5:!0000.00N/00000.00W>302 78 30 321 42
20251226224443YO5ZF-2>APRS,WIDE2-1,qAR,MISION:!0000.00N/00000.00W>205 80 28 315 42