APRS Packet Errors for W3BGE-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
20251013100708W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@131007z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251013101708W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@131017z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251013102709W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@131027z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251013120715W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@131207z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251013121715W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@131217z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251013122716W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@131227z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251013123716W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@131237z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251013124717W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@131247z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251013125717W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@131257z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251013130718W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@131307z3700.00N/05800.255r/A=000000SharkRF openSPOT3