APRS Packet Errors for BM7BGU-6 (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
20260209115824	BM7BGU-6>APIN20,TCPIP*,qAC,T2TAKAO:!2244.00N/12017.92E;PinPoint v2
20260209122824	BM7BGU-6>APIN20,TCPIP*,qAC,T2TAKAO:!2244.00N/12017.92E;PinPoint v2
20260209125824	BM7BGU-6>APIN20,TCPIP*,qAC,T2TAKAO:!2244.00N/12017.92E;PinPoint v2
20260209132824	BM7BGU-6>APIN20,TCPIP*,qAC,T2TAKAO:!2244.00N/12017.92E;PinPoint v2
20260209135824	BM7BGU-6>APIN20,TCPIP*,qAC,T2TAKAO:!2244.00N/12017.92E;PinPoint v2
20260209142824	BM7BGU-6>APIN20,TCPIP*,qAC,T2TAKAO:!2244.00N/12017.92E;PinPoint v2
20260209145824	BM7BGU-6>APIN20,TCPIP*,qAC,T2TAKAO:!2244.00N/12017.92E;PinPoint v2
20260209152824	BM7BGU-6>APIN20,TCPIP*,qAC,T2TAKAO:!2244.00N/12017.92E;PinPoint v2
20260209155825	BM7BGU-6>APIN20,TCPIP*,qAC,T2TAKAO:!2244.00N/12017.92E;PinPoint v2
20260209162825	BM7BGU-6>APIN20,TCPIP*,qAC,T2TAKAO:!2244.00N/12017.92E;PinPoint v2
20260209165825	BM7BGU-6>APIN20,TCPIP*,qAC,T2TAKAO:!2244.00N/12017.92E;PinPoint v2
20260209172825	BM7BGU-6>APIN20,TCPIP*,qAC,T2TAKAO:!2244.00N/12017.92E;PinPoint v2