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
20251219192558KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219193557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219194557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219195558KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219200557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219201557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219202558KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219203621KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219204557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219205558KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219210558KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219211557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219212931KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219213557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219214557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219215558KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219220602KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219221557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219222558KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219223557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219224557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219225558KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219230557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219231557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219232559KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219233557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219234557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251219235558KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251220000557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251220001557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251220002558KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251220003557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251220004557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251220005558KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251220010557KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251220011558KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W