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
20251103010926W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@030109z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251103011926W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@030119z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251103012928W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@030129z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251103013929W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@030139z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251103014930W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@030149z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251103015930W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@030159z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251103020930W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@030209z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251103021931W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@030219z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251103022932W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@030229z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251103023932W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@030239z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251103024933W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@030249z3700.00N/05800.255r/A=000000SharkRF openSPOT3
20251103025934W3BGE-10>APOSB,TCPIP*,qAS,W3BGE:@030259z3700.00N/05800.255r/A=000000SharkRF openSPOT3