APRS Packet Errors for K9COE-11 (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
20250916093310K9COE-11>ASOTU0,K6ERN,XE2SI-10,KF6ILA-10,WIDE2*,qAR,W6ZU-10:!3414.63N/1146.71W_180/000k000t059p000h82T2WX
20250916094704K9COE-11>APOTU0,K6ERN,XE2SI-10,KF6ILA-10,WIDE2*,qAO,KD6LPA:!3414.63N/1Q846.71W_ 12.3V 27C
20250916094705K9COE-11>APOTU0,K6ERN,XE2SI-10,KF6ILA-10,WIDE2*,qAR,W6ZU-10:!3414.63N/1)846.71W_180/000g000t059p000h82T2WX
20250916101935K9COE-11>APOTU0,K6ERN,KF6ILA-10*,qAR,KM6YBF-10:!3414.63N/11846.W1W_180/00g000t059p000h83T2WX
20250916101935K9COE-11>APOTU0,K6ERN,KF6ILA-10*,qAS,WM6Y-10:!3414.63N/11846.W1W_180/0
20250916102411K9COE-11>APOTU0,K6ERN,KF6ILA-10*,qAO,KD6LPA:!3414î63N/118T6.717_ 12.2V 26C
20250916104952K9COE-11>APOTU0,K6ERN,XE2SI-10,KF6ILA-10,WIDE2*,qAR,W6ZU-10:!3414.63N/1146.71W_180/000g000t059p000h81T2WX
20250916115715K9COE-11>APOTU0,K6ERN,XE2SI-10,KF6ILA-10,WIDE2*,qAR,KM6YBF-10:!3414.:3N/71846.71W_180/000g000t059p000h82T2WX
20250916122727K9COE-11>APOTU0,K6ERN,XE2SI-10,KF6ILA-10,WIDE2*,qAR,W6ZU-10:!3414.63N/©0846.71W_ 12.3V 26C