APRS Packet Errors for KP4SC-2 (last 24 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
20260314174910KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260314175911KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260314180910KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260314181910KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260314182911KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260314183910KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260314184910KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260314185911KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260314190910KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260314191910KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260314192911KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260314193910KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260314194910KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260314195911KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W