Who won Pacatiw vs Thang?
Jeremy Pacatiw beat Tial Thang by submission in the 2nd round during the main card of ONE Championship 164, on Saturday 3rd December 2022 at Singapore Indoor Stadium in Singapore.
The fight was scheduled to take place over 3 rounds in the Bantamweight division, which meant the weight limit was 135 pounds (9.6 stone or 61.2 KG).
Pacatiw vs Thang stats
Jeremy Pacatiw stepped into the octagon with a record of 10 wins, 4 losses and 0 draws, 2 of those wins coming by the way of knock out and 2 by submission.
Tial Thang made his way to the cage with a record of 3 wins, 1 loss and 0 draws, 1 of those win coming by knock out.
Jeremy Pacatiw's One Championship record stood at 2-1-0, while Tial Thang's came in at 3-2-0.
The stats suggested Thang had an advantage in power over Pacatiw, with a 33% knock out percentage over Pacatiw's 20%.
If the fight went to the ground, their records suggested Pacatiw had an advantage over Thang, with a 20% submission rate over Thang's 0%.
Jeremy Pacatiw was the older man by 28 years, at 28 years old.
Pacatiw was the more experienced professional fighter, having had 10 more fights, and made his debut in 2015, 3 years and 3 months earlier than Thang, whose first professional fight was in 2019. He had fought 24 more professional rounds, 38 to Thang's 14.
Activity check
Pacatiw's last 2 fights had come over a period of 3 years, 2 months and 4 days, meaning he had been fighting on average every 1 year, 7 months and 4 days. In those fights, he fought a total of 4 rounds, meaning that they had lasted 2 rounds on average.
Thang's last 4 fights had come over a period of 5 years, 6 months and 26 days, meaning he had been fighting on average every 1 year, 4 months and 24 days. In those fights, he fought a total of 9 rounds, meaning that they had lasted 2.3 rounds on average.
What were the odds on Pacatiw vs Thang?
Jeremy Pacatiw was a 2/7 (-340) favourite going into the contest, while Tial Thang made his way into the ring at 12/5 (+240) with oddsmakers.
Leave a Reply
You must be logged in to post a comment.