Tape rankings @ Light Heavyweight
Magomed Ankalaev vs Ion Cutelaba report
Who won Ankalaev vs Cutelaba?
Magomed Ankalaev beat Ion Cutelaba by during the main card of UFC 254, on Saturday 24th October 2020 at UFC Fight Island in Abu Dhabi.
The scorecards were announced as in favor of winner Magomed Ankalaev.
The fight was scheduled to take place over 3 rounds in the Light Heavyweight division, which meant the weight limit was 205 pounds (14.6 stone or 93 KG).
Ankalaev vs Cutelaba stats
Magomed Ankalaev stepped into the octagon with a record of 13 wins, 1 loss and 0 draws, 8 of those wins coming by the way of knock out.
Ion Cutelaba made his way to the cage with an unblemished record of 0 wins and 0 draws.
The stats suggested Ankalaev had a massive power advantage over Cutelaba, boasting at 62% knock out percentage over Cutelaba's 0%.
If the fight went to the ground, their records suggested that Ankalaev and Cutelaba would have been pretty equal, both with a 0% submission rate.
Magomed Ankalaev was the older man by 1 year, at 30 years old.
Ankalaev had a height advantage of 2 inches over Cutelaba. Despite this, both fighters had equal reach.
Ankalaev was arguably the more experienced fighter, having had 14 more fights, and made his debut in 2014, 1 year and 9 months later than Cutelaba, whose first professional fight was in 2012. He had fought 4 more professional rounds, 44 to Cutelaba's 40.
Ankalaev's last 2 fights had come over a period of 4 years, 1 month and 8 days, meaning he had been fighting on average every 2 years and 18 days. In those fights, he fought a total of 4 rounds, meaning that they had lasted 2 rounds on average.
Cutelaba's last 4 fights had come over a period of 5 years, 9 months and 21 days, meaning he had been fighting on average every 1 year, 5 months and 14 days. In those fights, he fought a total of 5 rounds, meaning that they had lasted 1.3 rounds on average.
What were the odds on Ankalaev vs Cutelaba?
Sorry, we couldn’t find any historical odds for Ankalaev vs Cutelaba.
Leave a Reply
You must be logged in to post a comment.