APRS Packet Errors for BH4GWF-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
20260209094320	BH4GWF-10>APN000,TCPIP*,qAC,T2HAKATA:=3112.70N/12126.58EO145.775MHz 13.2V
20260209101320	BH4GWF-10>APN000,TCPIP*,qAC,T2HAKATA:=3112.70N/12126.58EO145.775MHz 13.2V
20260209104320	BH4GWF-10>APN000,TCPIP*,qAC,T2HAKATA:=3112.70N/12126.58EO145.775MHz 13.2V
20260209111320	BH4GWF-10>APN000,TCPIP*,qAC,T2HAKATA:=3112.70N/12126.58EO145.775MHz 13.2V
20260209114320	BH4GWF-10>APN000,TCPIP*,qAC,T2HAKATA:=3112.70N/12126.58EO145.775MHz 13.2V
20260209121320	BH4GWF-10>APN000,TCPIP*,qAC,T2HAKATA:=3112.70N/12126.58EO145.775MHz 13.2V
20260209124320	BH4GWF-10>APN000,TCPIP*,qAC,T2HAKATA:=3112.70N/12126.58EO145.775MHz 13.2V
20260209131320	BH4GWF-10>APN000,TCPIP*,qAC,T2HAKATA:=3112.70N/12126.58EO145.775MHz 13.2V
20260209134320	BH4GWF-10>APN000,TCPIP*,qAC,T2HAKATA:=3112.70N/12126.58EO145.775MHz 13.2V
20260209141321	BH4GWF-10>APN000,TCPIP*,qAC,T2HAKATA:=3112.70N/12126.58EO145.775MHz 13.2V
20260209144321	BH4GWF-10>APN000,TCPIP*,qAC,T2HAKATA:=3112.70N/12126.58EO145.775MHz 13.3V
20260209151321	BH4GWF-10>APN000,TCPIP*,qAC,T2HAKATA:=3112.70N/12126.58EO145.775MHz 13.2V