APRS Packet Errors for K9WS-11 (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
20260209133051K9WS-11>APRSMC,TCPIP*,qAR,K9WS-10:!3724.81N/12206.34W#k9ws-meshcom#k9ws-11/B=100
20260209140107K9WS-11>APRSMC,TCPIP*,qAR,K9WS-10:!3724.81N/12206.34W#k9ws-meshcom#k9ws-11/B=100
20260209143122K9WS-11>APRSMC,TCPIP*,qAR,K9WS-10:!3724.81N/12206.34W#k9ws-meshcom#k9ws-11/B=100
20260209150137K9WS-11>APRSMC,TCPIP*,qAR,K9WS-10:!3724.81N/12206.34W#k9ws-meshcom#k9ws-11/B=100
20260209153152K9WS-11>APRSMC,TCPIP*,qAR,K9WS-10:!3724.81N/12206.34W#k9ws-meshcom#k9ws-11/B=100
20260209160207K9WS-11>APRSMC,TCPIP*,qAR,K9WS-10:!3724.81N/12206.34W#k9ws-meshcom#k9ws-11/B=100
20260209163222K9WS-11>APRSMC,TCPIP*,qAR,K9WS-10:!3724.81N/12206.34W#k9ws-meshcom#k9ws-11/B=100
20260209170237K9WS-11>APRSMC,TCPIP*,qAR,K9WS-10:!3724.81N/12206.34W#k9ws-meshcom#k9ws-11/B=100
20260209173252K9WS-11>APRSMC,TCPIP*,qAR,K9WS-10:!3724.81N/12206.34W#k9ws-meshcom#k9ws-11/B=100
20260209180310K9WS-11>APRSMC,TCPIP*,qAR,K9WS-10:!3724.81N/12206.34W#k9ws-meshcom#k9ws-11/B=100
20260209183322K9WS-11>APRSMC,TCPIP*,qAR,K9WS-10:!3724.81N/12206.34W#k9ws-meshcom#k9ws-11/B=100
20260209190337K9WS-11>APRSMC,TCPIP*,qAR,K9WS-10:!3724.81N/12206.34W#k9ws-meshcom#k9ws-11/B=100