APRS Packet Errors for YO5ZY (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
20260218180353YO5ZY>APRS,WIDE2-1,qAR,WC4PEM-10:!0000.00N/00000.00W>423 76 -16 361 44
20260218182605YO5ZY>APRS,WIDE2-1,qAR,WC4PEM-12:!0000.00N/00000.00W>402 79 -20 365 44
20260218185013YO5ZY>APRS,WIDE2-1,qAR,CHIEFL:!0000.00N/00000.00W>452 69 -18 363 44
20260218191752YO5ZY>APRS,WIDE2-1,qAR,CHIEFL:!0000.00N/00000.00W>410 317 181 -22 1437 0 44
20260218194004YO5ZY>APRS,WIDE2-1,qAR,FLGBCH:!0000.00N/00000.00W>422 317 181 -17 1437 0 44
20260218200333YO5ZY>APRS,WIDE2-1,qAR,WC4PEM-10:!0000.00N/00000.00W>441 74 -15 357 44
20260218202259YO5ZY>APRS,WIDE2-1,qAR,KG9B-8:!0000.00N/00000.00W>407 84 -21 365 44
20260218204710YO5ZY>APRS,WIDE2-1,qAR,NI4CE-11:!0000.00N/00000.00W>408 81 -15 355 44
20260218211046YO5ZY>APRS,WIDE2-1,qAR,FLGBCH:!0000.00N/00000.00W>391 92 -16 355 44
20260218213648YO5ZY>APRS,WIDE2-1,qAR,FLGBCH:!0000.00N/00000.00W>362 83 -16 360 43
20260218220333YO5ZY>APRS,WIDE2-1,qAR,FLGBCH:!0000.00N/00000.00W>419 317 183 -11 1448 0 44
20260218223016YO5ZY>APRS,WIDE2-1,qAR,KO4PDI-1:!0000.00N/00000.00W>451 78 -7 346 44
20260218223700YO5ZY>APRS,KM4ZYG-10,WIDE2*,qAR,W4KBW:!0000.00N/00000.00W>451 78 -7 346 44
20260218230727YO5ZY>APRS,WIDE2-1,qAR,FLGBCH:!0000.00N/00000.00W>511 53 -2 340 44