Carlos Ulberg won the Ultimate Fighting Championship (UFC) light heavyweight title (up to 93 kg), but failed to take the belt home. The New Zealander reached the top of the category by heroically knocking out Jiri Prochazka at UFC 327. However, during the celebration party, he ended up losing the trophy amidst drunkenness.
In a statement to Fox Sports Australia, Ulberg revealed that, despite planning not to drink after the victory, he ended up getting carried away by the celebratory atmosphere. According to the fighter, the celebration began with a toast, evolved into a series of drinks, and ended with the disappearance of the championship belt.
See too
“I lost the belt, man. I don’t know where it is. After the victory, the plan was not to drink. But first someone comes and serves you champagne to celebrate. And then one thing leads to another and you’re downing shots. Then you take another, and another…”, said Carlos Ulberg.
Carlos Ulberg may have his title stripped by the UFC.
Although he lost the belt during the celebration, Carlos Ulberg is at serious risk of also losing his UFC champion status. This is because, during his fight with Jiri Prochazka , the New Zealander suffered a torn anterior cruciate ligament (ACL) in his knee, an injury that could keep him out of the octagon for an estimated nine to twelve months. The recovery time may force the organization to create an interim belt or even strip him of the undisputed title until the athlete is fit to return.
If Ulberg's departure from the championship is confirmed, names like Paulo Borrachinha and Magomed Ankalaev appear as public favorites to challenge for the belt. In addition to them, Khamzat Chimaev , the current middleweight champion (up to 83,9 kg), also emerges as a possible candidate; however, he will need to defend his title in the main event of UFC 328 against Sean Strickland on May 9th.
Exclusive: Michael PQD talks about his brutal UFC debut victory.
Read More about: Carlos Ulberg, Jiri Prochazka, Khamzat Chiaev, Magomed Ankalev, UFC 327




You need to log in to comment.