APRS Packet Errors for KN6YLK-7 (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
20260208151718KN6YLK-7>BEACON,qAR,N6CTA-7:!3356.12N/11720.72WB-1/B 145.05 DM13 FARPN
20260208154718KN6YLK-7>BEACON,qAR,N6CTA-7:!3356.12N/11720.72WB-1/B 145.05 DM13 FARPN
20260208161718KN6YLK-7>BEACON,qAR,N6CTA-7:!3356.12N/11720.72WB-1/B 145.05 DM13 FARPN
20260208164718KN6YLK-7>BEACON,qAR,N6CTA-7:!3356.12N/11720.72WB-1/B 145.05 DM13 FARPN
20260208171718KN6YLK-7>BEACON,qAR,N6CTA-7:!3356.12N/11720.72WB-1/B 145.05 DM13 FARPN
20260208174718KN6YLK-7>BEACON,qAR,N6CTA-7:!3356.12N/11720.72WB-1/B 145.05 DM13 FARPN
20260208181718KN6YLK-7>BEACON,qAR,N6CTA-7:!3356.12N/11720.72WB-1/B 145.05 DM13 FARPN
20260208184718KN6YLK-7>BEACON,qAR,N6CTA-7:!3356.12N/11720.72WB-1/B 145.05 DM13 FARPN
20260208191718KN6YLK-7>BEACON,qAR,N6CTA-7:!3356.12N/11720.72WB-1/B 145.05 DM13 FARPN
20260208194718KN6YLK-7>BEACON,qAR,N6CTA-7:!3356.12N/11720.72WB-1/B 145.05 DM13 FARPN
20260208201719KN6YLK-7>BEACON,qAR,N6CTA-7:!3356.12N/11720.72WB-1/B 145.05 DM13 FARPN
20260208204718KN6YLK-7>BEACON,qAR,N6CTA-7:!3356.12N/11720.72WB-1/B 145.05 DM13 FARPN