APRS Packet Errors for BA7NDB-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
20260209104251BA7NDB-15>APFMO2,TCPIP*,qAC,T2CS:=2308.98N/11313.94EIHello FMO
20260209111253BA7NDB-15>APFMO2,TCPIP*,qAC,T2CS:=2308.98N/11313.94EIHello FMO
20260209113940BA7NDB-15>APFMO0,TCPIP*,qAC,T2CS:=2308.98N/11313.94EIFMO-CLIENT,VOCAL,215,153,F5000KM,OL63pd,广州FMO中继,SIGN:vLzylxPo3fFP/HA6xLM0lw==
20260209114255BA7NDB-15>APFMO2,TCPIP*,qAC,T2CS:=2308.98N/11313.94EIHello FMO
20260209121257BA7NDB-15>APFMO2,TCPIP*,qAC,T2CS:=2308.98N/11313.94EIHello FMO
20260209124230BA7NDB-15>APFMO2,TCPIP*,qAC,T2CS:=2308.98N/11313.94EIHello FMO
20260209131232BA7NDB-15>APFMO2,TCPIP*,qAC,T2CS:=2308.98N/11313.94EIHello FMO
20260209134235BA7NDB-15>APFMO2,TCPIP*,qAC,T2CS:=2308.98N/11313.94EIHello FMO
20260209141236BA7NDB-15>APFMO2,TCPIP*,qAC,T2CS:=2308.98N/11313.94EIHello FMO
20260209144238BA7NDB-15>APFMO2,TCPIP*,qAC,T2CS:=2308.98N/11313.94EIHello FMO
20260209151239BA7NDB-15>APFMO2,TCPIP*,qAC,T2CS:=2308.98N/11313.94EIHello FMO
20260209154241BA7NDB-15>APFMO2,TCPIP*,qAC,T2CS:=2308.98N/11313.94EIHello FMO
20260209161242BA7NDB-15>APFMO2,TCPIP*,qAC,T2CS:=2308.98N/11313.94EIHello FMO