APRS Packet Errors for WB0QXW (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
20260209090159	WB0QXW>APWW11,TCPIP*,qAC,T2CAWEST:=3833.68N/09019.08W-WB0QXW.NET 145.210 and 444.150
20260209093200	WB0QXW>APWW11,TCPIP*,qAC,T2CAWEST:=3833.68N/09019.08W-WB0QXW.NET 145.210 and 444.150
20260209100201	WB0QXW>APWW11,TCPIP*,qAC,T2CAWEST:=3833.68N/09019.08W-WB0QXW.NET 145.210 and 444.150
20260209103202	WB0QXW>APWW11,TCPIP*,qAC,T2CAWEST:=3833.68N/09019.08W-WB0QXW.NET 145.210 and 444.150
20260209110203	WB0QXW>APWW11,TCPIP*,qAC,T2CAWEST:=3833.68N/09019.08W-WB0QXW.NET 145.210 and 444.150
20260209113203	WB0QXW>APWW11,TCPIP*,qAC,T2CAWEST:=3833.68N/09019.08W-WB0QXW.NET 145.210 and 444.150
20260209120204	WB0QXW>APWW11,TCPIP*,qAC,T2CAWEST:=3833.68N/09019.08W-WB0QXW.NET 145.210 and 444.150
20260209123204	WB0QXW>APWW11,TCPIP*,qAC,T2CAWEST:=3833.68N/09019.08W-WB0QXW.NET 145.210 and 444.150
20260209130205	WB0QXW>APWW11,TCPIP*,qAC,T2CAWEST:=3833.68N/09019.08W-WB0QXW.NET 145.210 and 444.150
20260209133205	WB0QXW>APWW11,TCPIP*,qAC,T2CAWEST:=3833.68N/09019.08W-WB0QXW.NET 145.210 and 444.150
20260209140206	WB0QXW>APWW11,TCPIP*,qAC,T2CAWEST:=3833.68N/09019.08W-WB0QXW.NET 145.210 and 444.150
20260209143206	WB0QXW>APWW11,TCPIP*,qAC,T2CAWEST:=3833.68N/09019.08W-WB0QXW.NET 145.210 and 444.150