APRS Packet Errors for BG5BVC-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
20260209143902	BG5BVC-10>APE32I,TCPIP*,qAC,T2YANTAI:/091439z2901.91N/11933.79Er APRS iGate 144.640Mhz
20260209150902	BG5BVC-10>APE32I,TCPIP*,qAC,T2YANTAI:/091509z2901.91N/11933.79Er APRS iGate 144.640Mhz
20260209153902	BG5BVC-10>APE32I,TCPIP*,qAC,T2YANTAI:/091539z2901.91N/11933.79Er APRS iGate 144.640Mhz
20260209160902	BG5BVC-10>APE32I,TCPIP*,qAC,T2YANTAI:/091609z2901.91N/11933.79Er APRS iGate 144.640Mhz
20260209163902	BG5BVC-10>APE32I,TCPIP*,qAC,T2YANTAI:/091639z2901.91N/11933.79Er APRS iGate 144.640Mhz
20260209170902	BG5BVC-10>APE32I,TCPIP*,qAC,T2YANTAI:/091709z2901.91N/11933.79Er APRS iGate 144.640Mhz
20260209173902	BG5BVC-10>APE32I,TCPIP*,qAC,T2YANTAI:/091739z2901.91N/11933.79Er APRS iGate 144.640Mhz
20260209180902	BG5BVC-10>APE32I,TCPIP*,qAC,T2YANTAI:/091809z2901.91N/11933.79Er APRS iGate 144.640Mhz
20260209183902	BG5BVC-10>APE32I,TCPIP*,qAC,T2YANTAI:/091839z2901.91N/11933.79Er APRS iGate 144.640Mhz
20260209190902	BG5BVC-10>APE32I,TCPIP*,qAC,T2YANTAI:/091909z2901.91N/11933.79Er APRS iGate 144.640Mhz
20260209193902	BG5BVC-10>APE32I,TCPIP*,qAC,T2YANTAI:/091939z2901.91N/11933.79Er APRS iGate 144.640Mhz
20260209200902	BG5BVC-10>APE32I,TCPIP*,qAC,T2YANTAI:/092009z2901.91N/11933.79Er APRS iGate 144.640Mhz