APRS Packet Errors for N4ACT (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
20260209103038N4ACT>APWW11,TCPIP*,qAC,T2CHILE:@103038h3558.13N/07538.52W-APRS-IS for Win32
20260209110038N4ACT>APWW11,TCPIP*,qAC,T2CHILE:@110038h3558.13N/07538.52W-APRS-IS for Win32
20260209113039N4ACT>APWW11,TCPIP*,qAC,T2CHILE:@113038h3558.13N/07538.52W-APRS-IS for Win32
20260209120039N4ACT>APWW11,TCPIP*,qAC,T2CHILE:@120039h3558.13N/07538.52W-APRS-IS for Win32
20260209123040N4ACT>APWW11,TCPIP*,qAC,T2CHILE:@123039h3558.13N/07538.52W-APRS-IS for Win32
20260209130041N4ACT>APWW11,TCPIP*,qAC,T2CHILE:@130040h3558.13N/07538.52W-APRS-IS for Win32
20260209133041N4ACT>APWW11,TCPIP*,qAC,T2CHILE:@133041h3558.13N/07538.52W-APRS-IS for Win32
20260209140042N4ACT>APWW11,TCPIP*,qAC,T2CHILE:@140042h3558.13N/07538.52W-APRS-IS for Win32
20260209143043N4ACT>APWW11,TCPIP*,qAC,T2CHILE:@143042h3558.13N/07538.52W-APRS-IS for Win32
20260209150043N4ACT>APWW11,TCPIP*,qAC,T2CHILE:@150043h3558.13N/07538.52W-APRS-IS for Win32
20260209153044N4ACT>APWW11,TCPIP*,qAC,T2CHILE:@153044h3558.13N/07538.52W-APRS-IS for Win32
20260209160044N4ACT>APWW11,TCPIP*,qAC,T2CHILE:@160044h3558.13N/07538.52W-APRS-IS for Win32