APRS Packet Errors for BA4SEX-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
20260209121504	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260209124505	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260209131507	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260209134509	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260209141511	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260209144513	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260209151514	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260209154516	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260209161520	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260209164519	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260209171521	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260209174522	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.