APRS Packet Errors for YO5ZG-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
20251214143641YO5ZG-12>APRS,WIDE2,qAR,EA8URL-10:!0000.00N/00000.00W>305 73 -9 354 40
20251214151137YO5ZG-12>APRS,WIDE2-1,qAR,EA8URL-10:!0000.00N/00000.00W>248 66 -7 352 41
20251214154242YO5ZG-12>APRS,WIDE2,qAR,EA8URL-10:!0000.00N/00000.00W>267 318 23 -4 1137 0 41 2
20251214161432YO5ZG-12>APRS,WIDE2-1,qAR,EA8URL-10:!0000.00N/00000.00W>242 71 -7 353 41
20251214164155YO5ZG-12>APRS,WIDE2-1,qAR,EA8URL-10:!0000.00N/00000.00W>254 318 24 -7 1137 0 41 2
20251214164932YO5ZG-12>APRS,WIDE2-1,qAR,EA8URL-10:!0000.00N/00000.00W>258 70 -6 350 41