APRS Packet Errors for BG6JXF-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
20260208151614	BG6JXF-15>APFMO2,TCPIP*,qAC,T2HK:=3446.34NF11343.43EiE1[欢迎通联]
20260208152938	BG6JXF-15>APFMO0,TCPIP*,qAC,T2HK:=3446.34NF11343.43EiFMO-CLIENT,BEACON,79,FREQ:438.5000,HEIGHT:6,RIG:Alinco DR-435,ANT:QTH 郑州,SIGN:FNxKDrKuX86F3bGFLWbQaA==
20260208154617	BG6JXF-15>APFMO2,TCPIP*,qAC,T2HK:=3446.34NF11343.43EiE1[欢迎通联]
20260208161619	BG6JXF-15>APFMO2,TCPIP*,qAC,T2HK:=3446.34NF11343.43EiE1[欢迎通联]
20260208164552	BG6JXF-15>APFMO2,TCPIP*,qAC,T2HK:=3446.34NF11343.43EiE1[欢迎通联]
20260208171554	BG6JXF-15>APFMO2,TCPIP*,qAC,T2HK:=3446.34NF11343.43EiE1[欢迎通联]
20260208174557	BG6JXF-15>APFMO2,TCPIP*,qAC,T2HK:=3446.34NF11343.43EiE1[欢迎通联]
20260208181600	BG6JXF-15>APFMO2,TCPIP*,qAC,T2HK:=3446.34NF11343.43EiE1[欢迎通联]
20260208184602	BG6JXF-15>APFMO2,TCPIP*,qAC,T2HK:=3446.34NF11343.43EiE1[欢迎通联]
20260208191605	BG6JXF-15>APFMO2,TCPIP*,qAC,T2HK:=3446.34NF11343.43EiE1[欢迎通联]
20260208194608	BG6JXF-15>APFMO2,TCPIP*,qAC,T2HK:=3446.34NF11343.43EiE1[欢迎通联]
20260208201610	BG6JXF-15>APFMO2,TCPIP*,qAC,T2HK:=3446.34NF11343.43EiE1[欢迎通联]
20260208204612	BG6JXF-15>APFMO2,TCPIP*,qAC,T2HK:=3446.34NF11343.43EiE1[欢迎通联]