APRS Packet Errors for JA2CCV-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
20260208164817JA2CCV-10>APX220,TCPIP*,qAC,T2HAKATA:=/<`aGq,S6x XASTIR 144.64Mhz(9k6) Owari-Asahi I-Gate
20260208171818JA2CCV-10>APX220,TCPIP*,qAC,T2HAKATA:=/<`aGq,S6x XASTIR 144.64Mhz(9k6) Owari-Asahi I-Gate
20260208174819JA2CCV-10>APX220,TCPIP*,qAC,T2HAKATA:=/<`aGq,S6x XASTIR 144.64Mhz(9k6) Owari-Asahi I-Gate
20260208181820JA2CCV-10>APX220,TCPIP*,qAC,T2HAKATA:=/<`aGq,S6x XASTIR 144.64Mhz(9k6) Owari-Asahi I-Gate
20260208184821JA2CCV-10>APX220,TCPIP*,qAC,T2HAKATA:=/<`aGq,S6x XASTIR 144.64Mhz(9k6) Owari-Asahi I-Gate
20260208191822JA2CCV-10>APX220,TCPIP*,qAC,T2HAKATA:=/<`aGq,S6x XASTIR 144.64Mhz(9k6) Owari-Asahi I-Gate
20260208194823JA2CCV-10>APX220,TCPIP*,qAC,T2HAKATA:=/<`aGq,S6x XASTIR 144.64Mhz(9k6) Owari-Asahi I-Gate
20260208201824JA2CCV-10>APX220,TCPIP*,qAC,T2HAKATA:=/<`aGq,S6x XASTIR 144.64Mhz(9k6) Owari-Asahi I-Gate
20260208204825JA2CCV-10>APX220,TCPIP*,qAC,T2HAKATA:=/<`aGq,S6x XASTIR 144.64Mhz(9k6) Owari-Asahi I-Gate
20260208211826JA2CCV-10>APX220,TCPIP*,qAC,T2HAKATA:=/<`aGq,S6x XASTIR 144.64Mhz(9k6) Owari-Asahi I-Gate
20260208214827JA2CCV-10>APX220,TCPIP*,qAC,T2HAKATA:=/<`aGq,S6x XASTIR 144.64Mhz(9k6) Owari-Asahi I-Gate
20260208221828JA2CCV-10>APX220,TCPIP*,qAC,T2HAKATA:=/<`aGq,S6x XASTIR 144.64Mhz(9k6) Owari-Asahi I-Gate