APRS Packet Errors for BG5JBF-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
20260208132500BG5JBF-15>APFMO2,TCPIP*,qAC,T2HK:=2841.92NF11550.30EiHello FMO
20260208135502BG5JBF-15>APFMO2,TCPIP*,qAC,T2HK:=2841.92NF11550.30EiHello FMO
20260208144808BG5JBF-15>APFMO0,TCPIP*,qAC,T2YANTAI:=2841.92NF11550.30EiFMO-CLIENT,ONLINE,712,447,F5000KM,NN70gc,甘肃集群中继,SIGN:ArAAjyRDfOTYntQBRkSGUg==
20260208145008BG5JBF-15>APFMO0,TCPIP*,qAC,T2YANTAI:=2841.92NF11550.30EiFMO-CLIENT,BEACON,712,FREQ:438.5000,HEIGHT:12,RIG:如意通6900,ANT:QTH南昌,SIGN:cSQvWU2Ua3KwB7ropkS0zA==
20260208145508BG5JBF-15>APFMO2,TCPIP*,qAC,T2YANTAI:=2841.92NF11550.30EiHello FMO
20260208152511BG5JBF-15>APFMO2,TCPIP*,qAC,T2YANTAI:=2841.92NF11550.30EiHello FMO
20260208155514BG5JBF-15>APFMO2,TCPIP*,qAC,T2YANTAI:=2841.92NF11550.30EiHello FMO
20260208162446BG5JBF-15>APFMO2,TCPIP*,qAC,T2YANTAI:=2841.92NF11550.30EiHello FMO
20260208165449BG5JBF-15>APFMO2,TCPIP*,qAC,T2YANTAI:=2841.92NF11550.30EiHello FMO
20260208172452BG5JBF-15>APFMO2,TCPIP*,qAC,T2YANTAI:=2841.92NF11550.30EiHello FMO