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
20260227235859KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228000900KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228001858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228002900KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228003859KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228004901KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228005859KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228010900KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228011858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228012859KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228013859KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228014858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228015900KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228020858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228021858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228022901KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228023858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228024900KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228025859KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228030858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228031858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228032859KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228033858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228034901KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228035859KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228040858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228041858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228042907KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228043858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228044900KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228045859KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228050858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228051900KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228052859KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228053858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260228054858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W