APRS Packet Errors for KK0TT-5 (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
20260208164632	KK0TT-5>APZMAG,WIDE1-1,qAR,KK0TT-8:@081645z4655.18NL09646.61Waaprstastic: !499ecd4d
20260208172232	KK0TT-5>APZMAG,WIDE1-1,qAR,KK0TT-8:@081721z4655.18NL09646.61Waaprstastic: !499ecd4d
20260208175833	KK0TT-5>APZMAG,WIDE1-1,qAR,KK0TT-8:@081757z4655.18NL09646.61Waaprstastic: !499ecd4d
20260208183433	KK0TT-5>APZMAG,WIDE1-1,qAR,KK0TT-8:@081833z4655.18NL09646.61Waaprstastic: !499ecd4d
20260208191033	KK0TT-5>APZMAG,WIDE1-1,qAR,KK0TT-8:@081909z4655.18NL09646.61Waaprstastic: !499ecd4d
20260208194633	KK0TT-5>APZMAG,WIDE1-1,qAR,KK0TT-8:@081945z4655.18NL09646.61Waaprstastic: !499ecd4d
20260208202233	KK0TT-5>APZMAG,WIDE1-1,qAR,KK0TT-8:@082021z4655.18NL09646.61Waaprstastic: !499ecd4d
20260208205833	KK0TT-5>APZMAG,WIDE1-1,qAR,KK0TT-8:@082057z4655.18NL09646.61Waaprstastic: !499ecd4d
20260208213433	KK0TT-5>APZMAG,WIDE1-1,qAR,KK0TT-8:@082133z4655.18NL09646.61Waaprstastic: !499ecd4d
20260208221033	KK0TT-5>APZMAG,WIDE1-1,qAR,KK0TT-8:@082209z4655.18NL09646.61Waaprstastic: !499ecd4d