APRS Packet Errors for BI4RAR-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
20260209092519BI4RAR-1>APFMO2,TCPIP*,qAC,T2YANTAI:=3146.65NF11959.28EiHello FMO，BI4RAR
20260209095522BI4RAR-1>APFMO2,TCPIP*,qAC,T2YANTAI:=3146.65NF11959.28EiHello FMO，BI4RAR
20260209102525BI4RAR-1>APFMO2,TCPIP*,qAC,T2YANTAI:=3146.65NF11959.28EiHello FMO，BI4RAR
20260209105527BI4RAR-1>APFMO2,TCPIP*,qAC,T2YANTAI:=3146.65NF11959.28EiHello FMO，BI4RAR
20260209112529BI4RAR-1>APFMO2,TCPIP*,qAC,T2YANTAI:=3146.65NF11959.28EiHello FMO，BI4RAR
20260209115532BI4RAR-1>APFMO2,TCPIP*,qAC,T2YANTAI:=3146.65NF11959.28EiHello FMO，BI4RAR
20260209122535BI4RAR-1>APFMO2,TCPIP*,qAC,T2YANTAI:=3146.65NF11959.28EiHello FMO，BI4RAR
20260209125538BI4RAR-1>APFMO2,TCPIP*,qAC,T2YANTAI:=3146.65NF11959.28EiHello FMO，BI4RAR
20260209132511BI4RAR-1>APFMO2,TCPIP*,qAC,T2YANTAI:=3146.65NF11959.28EiHello FMO，BI4RAR
20260209135514BI4RAR-1>APFMO2,TCPIP*,qAC,T2YANTAI:=3146.65NF11959.28EiHello FMO，BI4RAR
20260209142517BI4RAR-1>APFMO2,TCPIP*,qAC,T2YANTAI:=3146.65NF11959.28EiHello FMO，BI4RAR
20260209143247BI4RAR-1>APFMO0,TCPIP*,qAC,T2NANJING:=3146.65NF11959.28EiFMO-CLIENT,ONLINE,410,447,F5000KM,NN70gc,甘肃集群中继,SIGN:kGFh6/flXynW64k8NhOKeQ==
20260209145523BI4RAR-1>APFMO2,TCPIP*,qAC,T2NANJING:=3146.65NF11959.28EiHello FMO，BI4RAR