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
20251208080531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208081532KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208082531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208083531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208084532KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208085531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208090531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208091532KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208092531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208093531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208094532KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208095531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208100531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208101532KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208102531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208103531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208104532KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208105533KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208110656KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208111723KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208112636KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208113532KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208114542KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208115532KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208120531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208121534KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208122534KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208123533KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208124532KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208125532KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208130544KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208131532KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208132531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208133539KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208134532KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251208135531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W