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
20251223164239KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223165238KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223170238KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223171239KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223172238KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223173238KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223174239KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223175241KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223180238KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223181329KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223182240KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223183238KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223184240KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223185238KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223190238KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223191239KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223192239KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223193238KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223194239KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223195314KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223200239KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223201239KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223202241KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223203238KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223204239KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223205244KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223210242KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223211239KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223212239KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223213238KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223214240KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223215242KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223220239KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223221239KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223222239KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251223223240KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W