APRS Packet Errors for KP4SC-2 (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
20260917203903KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917204903KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917205904KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917211903KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917212904KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917213903KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917214903KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917215904KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917220903KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917221903KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917222904KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917223903KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917224903KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917225904KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917230903KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917231903KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917232904KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20260917233903KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W