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
20260208170005W7DBO-3>APRS,TCPIP*,qAC,T2NALA:/081655z4022.33N/11151.28W_139/...g003t045r000h61b10334
20260208180007W7DBO-3>APRS,TCPIP*,qAC,T2BC:/081755z4022.33N/11151.28W_144/...g005t047r000h57b10324
20260208190005W7DBO-3>APRS,TCPIP*,qAC,T2OREGON:/081855z4022.33N/11151.28W_157/...g006t052r000h44b10296
20260208200005W7DBO-3>APRS,TCPIP*,qAC,T2MCI:/081955z4022.33N/11151.28W_245/...g005t057r000h38b10268
20260208210007W7DBO-3>APRS,TCPIP*,qAC,T2TEXAS:/082055z4022.33N/11151.28W_211/...g005t059r000h34b10246
20260208220005W7DBO-3>APRS,TCPIP*,qAC,T2BC:/082155z4022.33N/11151.28W_124/...g005t065r000h29b10222