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
20251215194553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215195554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215200553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215201553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215202554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215203553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215204553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215205554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215210553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215211553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215212554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215213553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215214553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215215554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215220553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215221553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215222554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215223553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215224553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215225554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215230553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215231553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215232554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215233553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215234553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215235554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251216000553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251216001553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251216002554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251216003553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251216004553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251216010554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251216011554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251216012554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251216013553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W