APRS Packet Errors for YO5ZF-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
20251226175743YO5ZF-12>APRS,WIDE2-1,qAR,VE7AV-10:!0000.00N/00000.00W>423 73 39 311 42 a4 d1 46
20251226185449YO5ZF-12>APRS,WIDE2-1,qAR,VE7AV-10:!0000.00N/00000.00W>449 321 47 37 1242 0 42 1 a11 d0 47
20251226200259YO5ZF-12>APRS,WIDE2-1,qAR,VE7AV-10:!0000.00N/00000.00W>398 84 22 324 42
20251226212200YO5ZF-12>APRS,WIDE2-1,qAR,VE7AV-10:!0000.00N/00000.00W>438 77 31 321 42
20251226215720YO5ZF-12>APRS,WIDE2-1,qAR,DRMT39:!0000.00N/00000.00W>443 80 29 319 42
20251226231606YO5ZF-12>APRS,WIDE2-1,qAR,DRMT39:!0000.00N/00000.00W>425 321 51 28 1241 0 42 1
20251226231654YO5ZF-12>APRS,FRASER,BOER,WIDE2*,qAR,VE7LDR:!0000.00N/00000.00W>425 321 51 28 1241 0 42 1