APRS Packet Errors for JH9YVE-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
20260209110032JH9YVE-10>APU25N,TCPIP*,qAC,T2OSAKA:=Id& BPHG1020/144.64MHz 9600bps/144.66MHz 1200bps
20260209113032JH9YVE-10>APU25N,TCPIP*,qAC,T2OSAKA:=Id& BPHG1020/144.64MHz 9600bps/144.66MHz 1200bps
20260209120032JH9YVE-10>APU25N,TCPIP*,qAC,T2OSAKA:=Id& BPHG1020/144.64MHz 9600bps/144.66MHz 1200bps
20260209123032JH9YVE-10>APU25N,TCPIP*,qAC,T2OSAKA:=Id& BPHG1020/144.64MHz 9600bps/144.66MHz 1200bps
20260209130032JH9YVE-10>APU25N,TCPIP*,qAC,T2OSAKA:=Id& BPHG1020/144.64MHz 9600bps/144.66MHz 1200bps
20260209133032JH9YVE-10>APU25N,TCPIP*,qAC,T2OSAKA:=Id& BPHG1020/144.64MHz 9600bps/144.66MHz 1200bps
20260209140033JH9YVE-10>APU25N,TCPIP*,qAC,T2OSAKA:=Id& BPHG1020/144.64MHz 9600bps/144.66MHz 1200bps
20260209143033JH9YVE-10>APU25N,TCPIP*,qAC,T2OSAKA:=Id& BPHG1020/144.64MHz 9600bps/144.66MHz 1200bps
20260209150033JH9YVE-10>APU25N,TCPIP*,qAC,T2OSAKA:=Id& BPHG1020/144.64MHz 9600bps/144.66MHz 1200bps
20260209153033JH9YVE-10>APU25N,TCPIP*,qAC,T2OSAKA:=Id& BPHG1020/144.64MHz 9600bps/144.66MHz 1200bps
20260209160033JH9YVE-10>APU25N,TCPIP*,qAC,T2OSAKA:=Id& BPHG1020/144.64MHz 9600bps/144.66MHz 1200bps
20260209163033JH9YVE-10>APU25N,TCPIP*,qAC,T2OSAKA:=Id& BPHG1020/144.64MHz 9600bps/144.66MHz 1200bps