APRS Packet Errors for BG7KYM-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
20260208152119BG7KYM-1>APFMO2,TCPIP*,qAC,T2FZ:=2304.58NF11345.64EiHello MYISMY
20260208155120BG7KYM-1>APFMO2,TCPIP*,qAC,T2FZ:=2304.58NF11345.64EiHello MYISMY
20260208162121BG7KYM-1>APFMO2,TCPIP*,qAC,T2FZ:=2304.58NF11345.64EiHello MYISMY
20260208165123BG7KYM-1>APFMO2,TCPIP*,qAC,T2FZ:=2304.58NF11345.64EiHello MYISMY
20260208165811BG7KYM-1>APFMO0,TCPIP*,qAC,T2HK:=2304.58NF11345.64EiFMO-CLIENT,ONLINE,903,313,F5000KM,OM20ap,成都FMO中继,SIGN:URD4+CjY3+8f/DBr2CVLPQ==
20260208172118BG7KYM-1>APFMO2,TCPIP*,qAC,T2HK:=2304.58NF11345.64EiHello MYISMY
20260208175118BG7KYM-1>APFMO2,TCPIP*,qAC,T2HK:=2304.58NF11345.64EiHello MYISMY
20260208182119BG7KYM-1>APFMO2,TCPIP*,qAC,T2HK:=2304.58NF11345.64EiHello MYISMY
20260208185120BG7KYM-1>APFMO2,TCPIP*,qAC,T2HK:=2304.58NF11345.64EiHello MYISMY
20260208192121BG7KYM-1>APFMO2,TCPIP*,qAC,T2HK:=2304.58NF11345.64EiHello MYISMY
20260208195122BG7KYM-1>APFMO2,TCPIP*,qAC,T2HK:=2304.58NF11345.64EiHello MYISMY
20260208202123BG7KYM-1>APFMO2,TCPIP*,qAC,T2HK:=2304.58NF11345.64EiHello MYISMY
20260208205124BG7KYM-1>APFMO2,TCPIP*,qAC,T2HK:=2304.58NF11345.64EiHello MYISMY