APRS Packet Errors for BH4GLB-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
20260209130550BH4GLB-15>APFMO2,TCPIP*,qAC,T2HK:=3114.31N/12134.59EIHello FMO
20260209133554BH4GLB-15>APFMO2,TCPIP*,qAC,T2HK:=3114.31N/12134.59EIHello FMO
20260209140250BH4GLB-15>APFMO0,TCPIP*,qAC,T2HK:=3114.31N/12134.59EIFMO-CLIENT,ONLINE,589,447,F5000KM,NN70gc,甘肃集群中继,SIGN:NvBGA9qWDC10yE2D2+5oxw==
20260209140451BH4GLB-15>APFMO0,TCPIP*,qAC,T2HK:=3114.31N/12134.59EIFMO-CLIENT,BEACON,589,FREQ:145.1000,RIG:YAESU FT-818,ANT:QTH 上海,SIGN:fIcpGMQFz6AmRYbBESqj5A==
20260209140526BH4GLB-15>APFMO2,TCPIP*,qAC,T2HK:=3114.31N/12134.59EIHello FMO
20260209143529BH4GLB-15>APFMO2,TCPIP*,qAC,T2HK:=3114.31N/12134.59EIHello FMO
20260209150533BH4GLB-15>APFMO2,TCPIP*,qAC,T2HK:=3114.31N/12134.59EIHello FMO
20260209153540BH4GLB-15>APFMO2,TCPIP*,qAC,T2HK:=3114.31N/12134.59EIHello FMO
20260209160538BH4GLB-15>APFMO2,TCPIP*,qAC,T2HK:=3114.31N/12134.59EIHello FMO
20260209163541BH4GLB-15>APFMO2,TCPIP*,qAC,T2HK:=3114.31N/12134.59EIHello FMO
20260209170543BH4GLB-15>APFMO2,TCPIP*,qAC,T2HK:=3114.31N/12134.59EIHello FMO
20260209173545BH4GLB-15>APFMO2,TCPIP*,qAC,T2HK:=3114.31N/12134.59EIHello FMO
20260209180547BH4GLB-15>APFMO2,TCPIP*,qAC,T2HK:=3114.31N/12134.59EIHello FMO
20260209183549BH4GLB-15>APFMO2,TCPIP*,qAC,T2HK:=3114.31N/12134.59EIHello FMO