APRS Packet Errors for BG6UAZ-15 (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
20260208134558BG6UAZ-15>APFMO2,TCPIP*,qAC,T2CS:=3033.77N/11419.98EIHello 武汉190 FMO
20260208141600BG6UAZ-15>APFMO2,TCPIP*,qAC,T2CS:=3033.77N/11419.98EIHello 武汉190 FMO
20260208144604BG6UAZ-15>APFMO2,TCPIP*,qAC,T2CS:=3033.77N/11419.98EIHello 武汉190 FMO
20260208151606BG6UAZ-15>APFMO2,TCPIP*,qAC,T2CS:=3033.77N/11419.98EIHello 武汉190 FMO
20260208154609BG6UAZ-15>APFMO2,TCPIP*,qAC,T2CS:=3033.77N/11419.98EIHello 武汉190 FMO
20260208161612BG6UAZ-15>APFMO2,TCPIP*,qAC,T2CS:=3033.77N/11419.98EIHello 武汉190 FMO
20260208164615BG6UAZ-15>APFMO2,TCPIP*,qAC,T2CS:=3033.77N/11419.98EIHello 武汉190 FMO
20260208171618BG6UAZ-15>APFMO2,TCPIP*,qAC,T2CS:=3033.77N/11419.98EIHello 武汉190 FMO
20260208174619BG6UAZ-15>APFMO2,TCPIP*,qAC,T2CS:=3033.77N/11419.98EIHello 武汉190 FMO
20260208181620BG6UAZ-15>APFMO2,TCPIP*,qAC,T2CS:=3033.77N/11419.98EIHello 武汉190 FMO
20260208184622BG6UAZ-15>APFMO2,TCPIP*,qAC,T2CS:=3033.77N/11419.98EIHello 武汉190 FMO
20260208191623BG6UAZ-15>APFMO2,TCPIP*,qAC,T2CS:=3033.77N/11419.98EIHello 武汉190 FMO