APRS Packet Errors for BI7NAM-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
20260209144112	BI7NAM-10>APET51,TCPIP*,qAC,FOURTH:!2311.28N/11252.80ErSanshui aprs igate 144.640MHZ 12.5V
20260209151252	BI7NAM-10>APET51,TCPIP*,qAC,FOURTH:!2311.28N/11252.80ErSanshui aprs igate 144.640MHZ 12.5V
20260209154432	BI7NAM-10>APET51,TCPIP*,qAC,FOURTH:!2311.28N/11252.80ErSanshui aprs igate 144.640MHZ 12.5V
20260209161613	BI7NAM-10>APET51,TCPIP*,qAC,FOURTH:!2311.28N/11252.80ErSanshui aprs igate 144.640MHZ 12.5V
20260209164753	BI7NAM-10>APET51,TCPIP*,qAC,FOURTH:!2311.28N/11252.80ErSanshui aprs igate 144.640MHZ 12.5V
20260209171933	BI7NAM-10>APET51,TCPIP*,qAC,FOURTH:!2311.28N/11252.80ErSanshui aprs igate 144.640MHZ 12.5V
20260209175113	BI7NAM-10>APET51,TCPIP*,qAC,FOURTH:!2311.28N/11252.80ErSanshui aprs igate 144.640MHZ 12.5V
20260209182253	BI7NAM-10>APET51,TCPIP*,qAC,FOURTH:!2311.28N/11252.80ErSanshui aprs igate 144.640MHZ 12.5V
20260209185433	BI7NAM-10>APET51,TCPIP*,qAC,FOURTH:!2311.28N/11252.80ErSanshui aprs igate 144.640MHZ 12.5V
20260209200900	BI7NAM-10>APET51,TCPIP*,qAC,FOURTH:!2311.28N/11252.80ErSanshui aprs igate 144.640MHZ 12.5V