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
20251214090537KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214091538KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214092537KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214093537KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214094538KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214095537KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214100537KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214101538KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214102537KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214103537KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214104538KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214105537KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214110537KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214111538KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214112537KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214113537KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214114538KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214115537KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214120537KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214121538KP4SC-2>APN382,TCPIP*,qAC,T2OREGON:!1824.22NS06704.13W
20251214122537KP4SC-2>APN382,TCPIP*,qAC,T2CAWEST:!1824.22NS06704.13W
20251214123537KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20251214124538KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20251214125537KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20251214130537KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20251214131538KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20251214132537KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20251214133537KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20251214134538KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20251214135537KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20251214140537KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20251214141538KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20251214142537KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20251214143537KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20251214144538KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W
20251214145537KP4SC-2>APN382,TCPIP*,qAC,T2RDU:!1824.22NS06704.13W