APRS Packet Errors for BA4QGE-10 (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
20260208132426	BA4QGE-10>APN000,TCPIP*,qAC,T2NANJING:=3011.67N/12013.91EKOOOAAEE 145.400MHz 13.9V
20260208135426	BA4QGE-10>APN000,TCPIP*,qAC,T2NANJING:=3011.67N/12013.91EKOOOAAEE 145.400MHz 13.9V
20260208142426	BA4QGE-10>APN000,TCPIP*,qAC,T2NANJING:=3011.67N/12013.91EKOOOAAEE 145.400MHz 13.9V
20260208145426	BA4QGE-10>APN000,TCPIP*,qAC,T2NANJING:=3011.67N/12013.91EKOOOAAEE 145.400MHz 13.9V
20260208152426	BA4QGE-10>APN000,TCPIP*,qAC,T2NANJING:=3011.67N/12013.91EKOOOAAEE 145.400MHz 14.0V
20260208155426	BA4QGE-10>APN000,TCPIP*,qAC,T2NANJING:=3011.67N/12013.91EKOOOAAEE 145.400MHz 13.9V
20260208162426	BA4QGE-10>APN000,TCPIP*,qAC,T2NANJING:=3011.67N/12013.91EKOOOAAEE 145.400MHz 13.9V
20260208165426	BA4QGE-10>APN000,TCPIP*,qAC,T2NANJING:=3011.67N/12013.91EKOOOAAEE 145.400MHz 13.9V
20260208172426	BA4QGE-10>APN000,TCPIP*,qAC,T2NANJING:=3011.67N/12013.91EKOOOAAEE 145.400MHz 14.0V
20260208175426	BA4QGE-10>APN000,TCPIP*,qAC,T2NANJING:=3011.67N/12013.91EKOOOAAEE 145.400MHz 13.9V
20260208182426	BA4QGE-10>APN000,TCPIP*,qAC,T2NANJING:=3011.67N/12013.91EKOOOAAEE 145.400MHz 13.9V
20260208185426	BA4QGE-10>APN000,TCPIP*,qAC,T2NANJING:=3011.67N/12013.91EKOOOAAEE 145.400MHz 14.0V