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
20251206193530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206194530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206195530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206200530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206201530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206202530KP4SC-2>APN382,WIDE2-1,qAS,REDOEN:!1824.22NS06704.13W
20251206203530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206204530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206205530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206210530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206211531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206212533KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206213530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206214531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206215530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206220530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206221530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206222530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206223530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206224530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206225530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206230531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206231530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206232530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206233530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206234531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206235530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251207000530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251207001531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251207002530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251207003530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251207004531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251207005530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251207010530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251207011531KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251207012530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W