APRS Packet Errors for W0MUD-3 (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
20260220045249W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200452z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220050250W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200502z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220051251W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200512z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220052252W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200522z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220053253W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200532z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220054254W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200542z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220055255W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200552z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220060256W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200602z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220061256W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200612z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220062257W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200622z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220063258W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200632z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220064259W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200642z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220065300W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200652z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220070301W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200703z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220071301W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200713z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220072302W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200723z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220073303W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200733z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220074304W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200743z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220075304W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200753z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220080305W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200803z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220081306W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200813z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220082307W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200823z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220083307W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200833z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220084307W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200843z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220085308W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200853z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220090309W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200903z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220091310W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200913z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220092311W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@200923z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220100314W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@201003z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN
20260220101314W0MUD-3>APOSB,TCPIP*,qAS,W0MUD:@201013z4815.98N/06600.255x/A=000108Open Wires-X Node 146.460 DN