APRS Packet Errors for BG1GXG-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
20260209104649BG1GXG-15>APFMO2,TCPIP*,qAC,T2YANTAI:=3959.48NF11610.31EiBeijing FMO Radio
20260209111652BG1GXG-15>APFMO2,TCPIP*,qAC,T2YANTAI:=3959.48NF11610.31EiBeijing FMO Radio
20260209114655BG1GXG-15>APFMO2,TCPIP*,qAC,T2YANTAI:=3959.48NF11610.31EiBeijing FMO Radio
20260209121658BG1GXG-15>APFMO2,TCPIP*,qAC,T2YANTAI:=3959.48NF11610.31EiBeijing FMO Radio
20260209124631BG1GXG-15>APFMO2,TCPIP*,qAC,T2YANTAI:=3959.48NF11610.31EiBeijing FMO Radio
20260209131634BG1GXG-15>APFMO2,TCPIP*,qAC,T2YANTAI:=3959.48NF11610.31EiBeijing FMO Radio
20260209134637BG1GXG-15>APFMO2,TCPIP*,qAC,T2YANTAI:=3959.48NF11610.31EiBeijing FMO Radio
20260209141640BG1GXG-15>APFMO2,TCPIP*,qAC,T2YANTAI:=3959.48NF11610.31EiBeijing FMO Radio
20260209142014BG1GXG-15>APFMO0,TCPIP*,qAC,T2NANJING:=3959.48NF11610.31EiFMO-CLIENT,ONLINE,700,447,F5000KM,NN70gc,甘肃集群中继,SIGN:xdBBRCG3WGfSasw7pj4FSA==
20260209142214BG1GXG-15>APFMO0,TCPIP*,qAC,T2NANJING:=3959.48NF11610.31EiFMO-CLIENT,BEACON,700,FREQ:438.5000,HEIGHT:10,RIG:泉盛 P8668i,ANT:首都北京,SIGN:3F9+NEzAs/vegywx9wmK9A==
20260209144651BG1GXG-15>APFMO2,TCPIP*,qAC,T2NANJING:=3959.48NF11610.31EiBeijing FMO Radio