Justin Gonzales returned to the win column at Bellator 279, beating a hometown favorite in Kai Kamaka III.
It came down to a split decision on Saturday night in Honolulu, something that didn’t entirely sit well with “J-Train.”
“I don’t know what that one judge was talking about, 29-28 him [Kamaka]. I think I won all three rounds pretty decisively, but it is what it is,” he exclaimed following the fight. “Maybe a little home town love, switching the fight short notice— I can make a lot of excuses, but I’m not about that. Came in, and handled business.”
Despite the split decision, Gonazales c(13-1) was confident he had the win in the bag when the scores were read. And just confident in general.
“I’m confident, man, I believe in my skills. I know how hard I work, I’ve done a lot of sh*t that a lot of people wouldn’t do. So just, I was very confident coming in. I know Kai’s tough, man, I’ve got all the respect in the world for that guy, he’s a gamer. He’s a beast. So much love to him. But getting booed like that, forget ya’ll. I came here to handle business.”
After three years away, of course, the local crowd was bounce to get behind their guy.
Asked for his thoughts on where the win leaves him, and what comes next, Gonzales said that after his “hiccup” against Aaron Pico, the goal was the same as always.
“I think it’s a good win, man. A tough opponent, a pretty solid victory, look at my face, I don’t look too beat up. I think I’m fine. Shoot man, I said it once, I’ll say it again, anybody in that ranking system, I’m coming for ya’ll. I want that belt, my goals haven’t changed just because I’ve had a hiccup, and I’m back, baby.” Then, giving it another moment’s thought, he added “actually, Cody Law, I’d like to beat him up, maybe [Daniel] Weichel. Sh*t I don’t know man, whoever. Whoever the f*ck they give me.”
Or, putting it another way, the plan is now to “F*ck up everybody in my path, man. That’s what’s next.”
Watch the full Bellator 279 post-fight press conference with Justin Gonzales above. More coverage from the event can be found below.