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
20260220044851KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220045858KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220050851KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220051852KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220052854KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220053851KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220054851KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220055853KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220060851KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220061859KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220062852KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220063851KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220064857KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220065852KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220070851KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220071851KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220072852KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220073851KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220074853KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220075901KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220080859KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220081852KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220082911KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220083851KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220084851KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220085852KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220090851KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220091853KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W
20260220100856KP4SC-2>APN382,TCPIP*,qAC,T2CAEAST:!1824.22NS06704.13W