APRS Packet Errors for BG9DDY-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
20260209092525BG9DDY-15>APFMO2,TCPIP*,qAC,T2HK:=3423.85NF10903.68Ei日寒杆
20260209095529BG9DDY-15>APFMO2,TCPIP*,qAC,T2HK:=3423.85NF10903.68Ei日寒杆
20260209102531BG9DDY-15>APFMO2,TCPIP*,qAC,T2HK:=3423.85NF10903.68Ei日寒杆
20260209105534BG9DDY-15>APFMO2,TCPIP*,qAC,T2HK:=3423.85NF10903.68Ei日寒杆
20260209112536BG9DDY-15>APFMO2,TCPIP*,qAC,T2HK:=3423.85NF10903.68Ei日寒杆
20260209115539BG9DDY-15>APFMO2,TCPIP*,qAC,T2HK:=3423.85NF10903.68Ei日寒杆
20260209122542BG9DDY-15>APFMO2,TCPIP*,qAC,T2HK:=3423.85NF10903.68Ei日寒杆
20260209125545BG9DDY-15>APFMO2,TCPIP*,qAC,T2HK:=3423.85NF10903.68Ei日寒杆
20260209132548BG9DDY-15>APFMO2,TCPIP*,qAC,T2HK:=3423.85NF10903.68Ei日寒杆
20260209133136BG9DDY-15>APFMO0,TCPIP*,qAC,T2NANJING:=3423.85NF10903.68EiFMO-CLIENT,ONLINE,67,447,F5000KM,NN70gc,甘肃集群中继,SIGN:tJwFRmCctJNrenU+u2N54A==
20260209133337BG9DDY-15>APFMO0,TCPIP*,qAC,T2NANJING:=3423.85NF10903.68EiFMO-CLIENT,BEACON,67,FREQ:438.5000,HEIGHT:1,RIG:泉盛TK-118,ANT:短天线,SIGN:VR8c5eqNE9/6kdFs5PCbDA==
20260209135543BG9DDY-15>APFMO2,TCPIP*,qAC,T2NANJING:=3423.85NF10903.68Ei日寒杆
20260209142546BG9DDY-15>APFMO2,TCPIP*,qAC,T2NANJING:=3423.85NF10903.68Ei日寒杆
20260209145550BG9DDY-15>APFMO2,TCPIP*,qAC,T2NANJING:=3423.85NF10903.68Ei日寒杆