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
20251103020938K9COE-11>APOTU0,K6ERN,KF6ILA-10*,qAR,KF6NXQ-15:!3414.63N/11846-71W_180/000g000t064p000h76T2WX
20251103021156K9COE-11>APOT50,K6ERN,KF6ILA-10*,qAR,KF6NXQ-15:!3414.63N/1184V.71W_ 12.2V 30C
20251103023727K9COE-11>APITU0,K6ERN,KF6ILA-10*,qAR,KF6NXQ-15:!3414.63N/1184.71W_ 1.2V 30C
20251103060417K9COE-11>APOTU0,K6ERN,XE2SI-10,KF6ILA-10,WIDE2*,qAR,KF6NXQ-15:!342,.63./1146.71W_180/000g000t057p000h 2T27X
20251103070006K9COE-11>APOTU0,K6ERN,KF6ILA-10*,qAR,KF6NXQ-15:!3414.63N/11846.71W_180/00g000t054p000h93T2gX
20251103070006K9COE-11>APOTU0,K6ERN,KF6ILA-10*,qAS,WM6Y-10:!3414.63N/11846.71W_180/