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
20251205201529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205202529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205203529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205204529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205205529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205210529KP4SC-2>APN382,WIDE2-1,qAS,REDOEN:!1824.22NS06704.13W
20251205211538KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205212529KP4SC-2>APN382,WIDE2-1,qAS,REDOEN:!1824.22NS06704.13W
20251205213529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205214529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205215529KP4SC-2>APN382,WIDE2-1,qAS,REDOEN:!1824.22NS06704.13W
20251205220529KP4SC-2>APN382,WIDE2-1,qAS,REDOEN:!1824.22NS06704.13W
20251205221529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205222529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205223529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205224529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205225529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205230529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205231530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205232529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205233529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205234530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251205235529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206000529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206001530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206002529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206003529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206004530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206005529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206010529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206011530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206012529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206013529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206014530KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206015529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251206020529KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W