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
20260318183914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318184914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318185917KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318190914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318191914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318192915KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318193914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318194914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318195918KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318200915KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318201914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318202916KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318203914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318204914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318205915KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318210914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318211914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318212915KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318213914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318214914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318215915KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318220914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318221914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318222915KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318223914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318224914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318225915KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318230914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318231914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318232915KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318233915KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318234914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260318235915KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260319000914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260319001914KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20260319002915KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W