APRS Packet Errors for YO5ZV-6 (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
20260314152738	YO5ZV-6>APRS,WIDE2-1,qAO,TF3VP-10:!0000.00N/00000.00W>205 346 517 -1 1317 0 43
20260314153124	YO5ZV-6>APRS,WIDE2-1,qAO,TF3VP-10:!0000.00N/00000.00W>226 76 0 363 43
20260314155727	YO5ZV-6>APRS,WIDE2-1,qAO,TF3VP-10:!0000.00N/00000.00W>254 75 0 352 43
20260314160442	YO5ZV-6>APRS,WIDE2-1,qAO,TF3VP-10:!0000.00N/00000.00W>229 72 -1 374 43
20260314163415	YO5ZV-6>APRS,WIDE2-1,qAR,TF3IRA-1:!0000.00N/00000.00W>251 76 0 372 43
20260314164130	YO5ZV-6>APRS,WIDE2-1,qAR,TF3IRA-1:!0000.00N/00000.00W>270 74 0 338 43
20260314175330	YO5ZV-6>APRS,WIDE2-1,qAR,TF3IRA-1:!0000.00N/00000.00W>783 66 1 349 42
20260314180042	YO5ZV-6>APRS,WIDE2-1,qAR,TF3IRA-1:!0000.00N/00000.00W>266 63 0 371 43