APRS Packet Errors for KC7IZH-1 (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
20260209150640KC7IZH-1>APWW11,TCPIP*,qAC,T2CHILE:@150638h4542.06N/12241.23W-APRS-IS for Win32
20260209153440KC7IZH-1>APWW11,TCPIP*,qAC,T2CHILE:@153438h4542.06N/12241.23W-APRS-IS for Win32
20260209160241KC7IZH-1>APWW11,TCPIP*,qAC,T2CHILE:@160238h4542.06N/12241.23W-APRS-IS for Win32
20260209163041KC7IZH-1>APWW11,TCPIP*,qAC,T2CHILE:@163038h4542.06N/12241.23W-APRS-IS for Win32
20260209165841KC7IZH-1>APWW11,TCPIP*,qAC,T2CHILE:@165839h4542.06N/12241.23W-APRS-IS for Win32
20260209172641KC7IZH-1>APWW11,TCPIP*,qAC,T2CHILE:@172639h4542.06N/12241.23W-APRS-IS for Win32
20260209175442KC7IZH-1>APWW11,TCPIP*,qAC,T2CHILE:@175439h4542.06N/12241.23W-APRS-IS for Win32
20260209182242KC7IZH-1>APWW11,TCPIP*,qAC,T2CHILE:@182239h4542.06N/12241.23W-APRS-IS for Win32
20260209185042KC7IZH-1>APWW11,TCPIP*,qAC,T2CHILE:@185039h4542.06N/12241.23W-APRS-IS for Win32
20260209191842KC7IZH-1>APWW11,TCPIP*,qAC,T2CHILE:@191840h4542.06N/12241.23W-APRS-IS for Win32
20260209194642KC7IZH-1>APWW11,TCPIP*,qAC,T2CHILE:@194640h4542.06N/12241.23W-APRS-IS for Win32
20260209201443KC7IZH-1>APWW11,TCPIP*,qAC,T2CHILE:@201440h4542.06N/12241.23W-APRS-IS for Win32
20260209204243KC7IZH-1>APWW11,TCPIP*,qAC,T2CHILE:@204240h4542.06N/12241.23W-APRS-IS for Win32