APRS Packet Errors for W7DJS-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
20260208143105W7DJS-10>APWW11,TCPIP*,qAC,T2SPAIN:@143104h3337.60N/11226.03WZPHG7030APRS-IS for Win32
20260208150105W7DJS-10>APWW11,TCPIP*,qAC,T2SPAIN:@150104h3337.60N/11226.03WZPHG7030APRS-IS for Win32
20260208153105W7DJS-10>APWW11,TCPIP*,qAC,T2SPAIN:@153104h3337.60N/11226.03WZPHG7030APRS-IS for Win32
20260208160105W7DJS-10>APWW11,TCPIP*,qAC,T2SPAIN:@160104h3337.60N/11226.03WZPHG7030APRS-IS for Win32
20260208163105W7DJS-10>APWW11,TCPIP*,qAC,T2SPAIN:@163104h3337.60N/11226.03WZPHG7030APRS-IS for Win32
20260208170105W7DJS-10>APWW11,TCPIP*,qAC,T2SPAIN:@170104h3337.60N/11226.03WZPHG7030APRS-IS for Win32
20260208173105W7DJS-10>APWW11,TCPIP*,qAC,T2SPAIN:@173104h3337.60N/11226.03WZPHG7030APRS-IS for Win32
20260208180106W7DJS-10>APWW11,TCPIP*,qAC,T2SPAIN:@180104h3337.60N/11226.03WZPHG7030APRS-IS for Win32
20260208183106W7DJS-10>APWW11,TCPIP*,qAC,T2SPAIN:@183104h3337.60N/11226.03WZPHG7030APRS-IS for Win32
20260208190106W7DJS-10>APWW11,TCPIP*,qAC,T2SPAIN:@190105h3337.60N/11226.03WZPHG7030APRS-IS for Win32
20260208193106W7DJS-10>APWW11,TCPIP*,qAC,T2SPAIN:@193105h3337.60N/11226.03WZPHG7030APRS-IS for Win32
20260208200106W7DJS-10>APWW11,TCPIP*,qAC,T2SPAIN:@200105h3337.60N/11226.03WZPHG7030APRS-IS for Win32