APRS Packet Errors for BG9JTK-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
20260209092340	BG9JTK-15>APFMO2,TCPIP*,qAC,T2NANJING:=3602.04N/10350.54EIBG9JTK
20260209095344	BG9JTK-15>APFMO2,TCPIP*,qAC,T2NANJING:=3602.04N/10350.54EIBG9JTK
20260209102346	BG9JTK-15>APFMO2,TCPIP*,qAC,T2NANJING:=3602.04N/10350.54EIBG9JTK
20260209105349	BG9JTK-15>APFMO2,TCPIP*,qAC,T2NANJING:=3602.04N/10350.54EIBG9JTK
20260209112352	BG9JTK-15>APFMO2,TCPIP*,qAC,T2NANJING:=3602.04N/10350.54EIBG9JTK
20260209115355	BG9JTK-15>APFMO2,TCPIP*,qAC,T2NANJING:=3602.04N/10350.54EIBG9JTK
20260209122358	BG9JTK-15>APFMO2,TCPIP*,qAC,T2NANJING:=3602.04N/10350.54EIBG9JTK
20260209125331	BG9JTK-15>APFMO2,TCPIP*,qAC,T2NANJING:=3602.04N/10350.54EIBG9JTK
20260209132334	BG9JTK-15>APFMO2,TCPIP*,qAC,T2NANJING:=3602.04N/10350.54EIBG9JTK
20260209135337	BG9JTK-15>APFMO2,TCPIP*,qAC,T2NANJING:=3602.04N/10350.54EIBG9JTK
20260209141017	BG9JTK-15>APN000,TCPIP*,qAC,T2OSAKA:=3602.29N/10350.85EF082/003大家好
20260209142016	BG9JTK-15>APN000,TCPIP*,qAC,T2OSAKA:=3602.29N/10350.86EK075/003大家好
20260209142340	BG9JTK-15>APFMO2,TCPIP*,qAC,T2NANJING:=3602.04N/10350.54EIBG9JTK
20260209145343	BG9JTK-15>APFMO2,TCPIP*,qAC,T2NANJING:=3602.04N/10350.54EIBG9JTK