APRS Packet Errors for W7DBO-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
20260209120006W7DBO-3>APRS,TCPIP*,qAC,T2OREGON:/091155z4022.33N/11151.28W_270/...g002t037r000h67b10250
20260209130005W7DBO-3>APRS,TCPIP*,qAC,T2MCI:/091255z4022.33N/11151.28W_083/...g002t036r000h71b10259
20260209140005W7DBO-3>APRS,TCPIP*,qAC,T2CAWEST:/091355z4022.33N/11151.28W_238/...g002t036r000h73b10258
20260209150005W7DBO-3>APRS,TCPIP*,qAC,T2MCI:/091455z4022.33N/11151.28W_.../...g000t037r000h72b10258
20260209160006W7DBO-3>APRS,TCPIP*,qAC,T2CAEAST:/091555z4022.33N/11151.28W_091/...g002t040r000h68b10250
20260209170005W7DBO-3>APRS,TCPIP*,qAC,T2TEXAS:/091655z4022.33N/11151.28W_122/...g010t046r000h62b10243