APRS Packet Errors for BI4NRO-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
20260209132935	BI4NRO-10>APN000,TCPIP*,qAC,T2OSAKA:=3506.68N/11708.46Er大美滕州欢迎您 438.500MHz 13.8V
20260209135935	BI4NRO-10>APN000,TCPIP*,qAC,T2OSAKA:=3506.68N/11708.46Er大美滕州欢迎您 438.500MHz 13.8V
20260209142935	BI4NRO-10>APN000,TCPIP*,qAC,T2OSAKA:=3506.68N/11708.46Er大美滕州欢迎您 438.500MHz 13.9V
20260209145935	BI4NRO-10>APN000,TCPIP*,qAC,T2OSAKA:=3506.68N/11708.46Er大美滕州欢迎您 438.500MHz 13.9V
20260209152935	BI4NRO-10>APN000,TCPIP*,qAC,T2OSAKA:=3506.68N/11708.46Er大美滕州欢迎您 438.500MHz 13.9V
20260209155935	BI4NRO-10>APN000,TCPIP*,qAC,T2OSAKA:=3506.68N/11708.46Er大美滕州欢迎您 438.500MHz 13.8V
20260209162935	BI4NRO-10>APN000,TCPIP*,qAC,T2OSAKA:=3506.68N/11708.46Er大美滕州欢迎您 438.500MHz 13.8V
20260209165935	BI4NRO-10>APN000,TCPIP*,qAC,T2OSAKA:=3506.68N/11708.46Er大美滕州欢迎您 438.500MHz 13.9V
20260209172935	BI4NRO-10>APN000,TCPIP*,qAC,T2OSAKA:=3506.68N/11708.46Er大美滕州欢迎您 438.500MHz 13.9V
20260209175935	BI4NRO-10>APN000,TCPIP*,qAC,T2OSAKA:=3506.68N/11708.46Er大美滕州欢迎您 438.500MHz 13.9V
20260209182935	BI4NRO-10>APN000,TCPIP*,qAC,T2OSAKA:=3506.68N/11708.46Er大美滕州欢迎您 438.500MHz 13.9V
20260209185935	BI4NRO-10>APN000,TCPIP*,qAC,T2OSAKA:=3506.68N/11708.46Er大美滕州欢迎您 438.500MHz 13.9V