APRS Packet Errors for KB2MFS-2 (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
20260208131528	KB2MFS-2>APWW11,TCPIP*,qAC,T2CHILE:@131527h3622.49N/08720.62WlAPRS-IS for Win32
20260208134529	KB2MFS-2>APWW11,TCPIP*,qAC,T2CHILE:@134528h3622.49N/08720.62WlAPRS-IS for Win32
20260208141529	KB2MFS-2>APWW11,TCPIP*,qAC,T2CHILE:@141528h3622.49N/08720.62WlAPRS-IS for Win32
20260208144530	KB2MFS-2>APWW11,TCPIP*,qAC,T2CHILE:@144529h3622.49N/08720.62WlAPRS-IS for Win32
20260208151531	KB2MFS-2>APWW11,TCPIP*,qAC,T2CHILE:@151530h3622.49N/08720.62WlAPRS-IS for Win32
20260208154531	KB2MFS-2>APWW11,TCPIP*,qAC,T2CHILE:@154530h3622.49N/08720.62WlAPRS-IS for Win32
20260208161532	KB2MFS-2>APWW11,TCPIP*,qAC,T2CHILE:@161531h3622.49N/08720.62WlAPRS-IS for Win32
20260208164532	KB2MFS-2>APWW11,TCPIP*,qAC,T2CHILE:@164531h3622.49N/08720.62WlAPRS-IS for Win32
20260208171533	KB2MFS-2>APWW11,TCPIP*,qAC,T2CHILE:@171532h3622.49N/08720.62WlAPRS-IS for Win32
20260208174534	KB2MFS-2>APWW11,TCPIP*,qAC,T2CHILE:@174533h3622.49N/08720.62WlAPRS-IS for Win32
20260208181535	KB2MFS-2>APWW11,TCPIP*,qAC,T2CHILE:@181533h3622.49N/08720.62WlAPRS-IS for Win32
20260208184535	KB2MFS-2>APWW11,TCPIP*,qAC,T2CHILE:@184534h3622.49N/08720.62WlAPRS-IS for Win32