APRS Packet Errors for OE8SQK-10 (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
20260209092317OE8SQK-10>APDW17,TCPIP*,qAC,FIRST:!4646.17N/01449.54E#APRS iGate - Blaiken, Sankt Andrae
20260209095316OE8SQK-10>APDW17,TCPIP*,qAC,FIRST:!4646.17N/01449.54E#APRS iGate - Blaiken, Sankt Andrae
20260209102316OE8SQK-10>APDW17,TCPIP*,qAC,FIRST:!4646.17N/01449.54E#APRS iGate - Blaiken, Sankt Andrae
20260209105316OE8SQK-10>APDW17,TCPIP*,qAC,FIRST:!4646.17N/01449.54E#APRS iGate - Blaiken, Sankt Andrae
20260209112316OE8SQK-10>APDW17,TCPIP*,qAC,FIRST:!4646.17N/01449.54E#APRS iGate - Blaiken, Sankt Andrae
20260209115316OE8SQK-10>APDW17,TCPIP*,qAC,FIRST:!4646.17N/01449.54E#APRS iGate - Blaiken, Sankt Andrae
20260209122317OE8SQK-10>APDW17,TCPIP*,qAC,FIRST:!4646.17N/01449.54E#APRS iGate - Blaiken, Sankt Andrae
20260209125316OE8SQK-10>APDW17,TCPIP*,qAC,FIRST:!4646.17N/01449.54E#APRS iGate - Blaiken, Sankt Andrae
20260209132317OE8SQK-10>APDW17,TCPIP*,qAC,FIRST:!4646.17N/01449.54E#APRS iGate - Blaiken, Sankt Andrae
20260209135316OE8SQK-10>APDW17,TCPIP*,qAC,FIRST:!4646.17N/01449.54E#APRS iGate - Blaiken, Sankt Andrae
20260209142317OE8SQK-10>APDW17,TCPIP*,qAC,FIRST:!4646.17N/01449.54E#APRS iGate - Blaiken, Sankt Andrae
20260209145316OE8SQK-10>APDW17,TCPIP*,qAC,FIRST:!4646.17N/01449.54E#APRS iGate - Blaiken, Sankt Andrae