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
20251215124539KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215125538KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215130538KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215131539KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215132538KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215133538KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215134539KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215135538KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215140538KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215141539KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215142538KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215143553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215144553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215145554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215150553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215151553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215152554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215153553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215154553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215155554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215160553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215161553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215162554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215163553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215164553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215165554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215170553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215171553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215172554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215173553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215174553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215175554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215180553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215181553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215182554KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W
20251215183553KP4SC-2>APN382,TCPIP*,qAC,T2USANW:!1824.22NS06704.13W