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
20251202234527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251202235526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203000526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203001527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203002526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203003526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203004527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203005527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203010526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203011527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203012526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203013526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203014527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203015527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203020526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203021527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203022527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203023526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203024527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203025526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203030526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203031527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203032526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203033526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203034527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203035526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203040526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203041527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203042526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203043527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203044527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203045526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203050526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203051527KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203052526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251203053526KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W