Who won Arlovski vs Struve?
Andrei Arlovski beat Stefan Struve by unanimous decision in their 3 round contest during the main card of UFC 222, on Saturday 3rd March 2018 at T-Mobile Arena in Las Vegas.
The scorecards were announced in favor of the winner Andrei Arlovski.
The fight was scheduled to take place over 3 rounds in the Heavyweight division, which meant the weight limit was 265 pounds (18.9 stone or 120.2 KG).
Arlovski vs Struve stats
Andrei Arlovski stepped into the octagon with a record of 26 wins, 15 losses and 0 draws, 17 of those wins coming by the way of knock out and 3 by submission.
Stefan Struve made his way to the cage with a record of 28 wins, 9 losses and 0 draws, 8 of those wins coming by knock out and 17 by submission.
This was Andrei Arlovski's 42nd fight in the UFC, having made his debut for the promotion in 2000.
Andrei Arlovski's UFC record stood at 23-18-0, while Stefan Struve's came in at 13-11-0.
The stats suggested Arlovski had a massive power advantage over Struve, boasting a 65% knock out percentage over Struve's 29%.
If the fight went to the ground, their records suggested Struve had a massive advantage over Arlovski, boasting a 61% submission rate over Arlovski's 12%.
Andrei Arlovski was the older man by 9 years, at 45 years old.
Struve had a height advantage of 8 inches over Arlovski. That also extended to a 8-inch reach advantage.
Arlovski was the more experienced professional fighter, having had 4 more fights, and made his debut in 1999, 5 years and 11 months earlier than Struve, whose first professional fight was in 2005. He had fought 64 more professional rounds, 130 to Struve's 66.
Activity check
Arlovski's last 3 fights had come over a period of 7 years, 10 months and 26 days, meaning he had been fighting on average every 2 years, 7 months and 19 days. In those fights, he fought a total of 7 rounds, meaning that they had lasted 2.3 rounds on average.
What were the odds on Arlovski vs Struve?
Sorry, we couldn’t find any historical odds for Arlovski vs Struve.
Leave a Reply
You must be logged in to post a comment.