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
20260208131524	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260208134525	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260208141527	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260208144529	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260208151530	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260208154503	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260208161503	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260208164505	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260208171506	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260208174507	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260208181509	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.
20260208184510	BA4SEX-15>APFMO2,TCPIP*,qAC,T2NANJING:=3111.37N/12128.70EIHello,BA4SEX on FMO.