APRS Packet Errors for K6ARC-3 (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
20260403195649K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3
20260403201149K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3
20260403202649K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3
20260403204149K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3
20260403205649K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3
20260403212653K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3
20260403214152K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3
20260403221154K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3
20260403222655K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3
20260403225657K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3
20260403231158K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3
20260403234200K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3
20260403235702K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3
20260404002703K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3
20260404005707K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3
20260404011207K6ARC-3>APTT4,ACARC-1*,WIDE2-1,qAo,N3CKF-2:;!K6ARC! Digi3