Mohammad Rizwan has raised eyebrows for his batting approach in Pakistan's failed chase of 184 against South Africa, consuming 50 balls to reach his fifty in a game that they eventually lost by 11 runs in Durban.
Rizwan was at 46 off 49 at one point, with the required run-rate shooting up to 15 per over, before he hit a six to reach his 31st T20I fifty. He ended with a 62-ball 74 while seven other batters finished with single-digit scores. The eventual strike rate of 119.35, after facing more than half the deliveries, highlighted that his knock might have done more harm than good.
Rizwan's strike rate was the third-lowest he has finished on in a fifty-plus knock, having also hit a run-a-ball unbeaten 53 against Canada in the T20 World Cup this year. That was the slowest fifty ever in the tournament's history. Two years ago, he managed a 49-ball 55 in a 23-run loss to Sri Lanka.
Rizwan goes slow, takes 50 balls to reach fifty
Having lost his opening partner Babar Azam for a four-ball duck, Rizwan took his time to get going. He ambled to eight off 14 before he hit his first boundary, and worked the ball around to 36 off 44, before he hit the next one for a six. In the 17th over, he also seemingly started getting affected by cramps.
74(62) chasing 184 means team mates & extras (which got them closer) need to score 110(58) = at 190 SR.
— Dan Weston (@SAAdvantage) December 10, 2024
Another way of looking at it - SA scored 24 boundaries, Rizwan scored 8 in 62 balls so to tie the boundary count Pakistan’s other batters needed 16 in 58 balls (27.5%) https://t.co/7PUyCgbRU5
He hit five fours and three sixes (one off a free-hit) in all: three of those fours came in the 19th over, with 31 needed off 12. He was dismissed off the second ball of the final over, leaving the tailenders with 18 to get off four.
It turned out to be the second-slowest 70-plus score by a captain in a T20I chase, with only Kane Williamson (70 off 60) having a worse strike rate during his 2016 knock against Pakistan.
This year, Rizwan's strike rate stands at 118.12 from 19 T20I innings.
Slowest T20I knocks by a Full-Member batter facing 60+ balls in a chase:
| Player | Runs | Balls | Strike rate | v Team | Year |
| G Gambhir (IND) | 56* | 60 | 93.33 | v Australia | 2012 |
| KS Williamson (NZ) | 70 | 60 | 116.66 | v Pakistan | 2016 |
| Sarfaraz Ahmed (PAK) | 76* | 64 | 118.75 | v New Zealand | 2014 |
| Mohammad Rizwan (PAK) | 74 | 62 | 119.35 | v South Africa | 2024 |
| W Madhevere (ZIM) | 73* | 61 | 119.67 | v Namibia | 2022 |
As expected, there was plenty of furore on social media:
Don’t let 74 off 62 balls fool you, this match was lost by Rizwan & no one else, he was 46 off 49 balls, scored 28 off last 13 balls when the game was almost lost, most batters lost their wickets because of Rizwan’s selfishness, criminal innings
— Osama. (@ashaqeens) December 10, 2024
Ramiz calling Rizwan's knock "A very good effort" is a example why we haven't just stagnated but gone backwards in T20 cricket. We don't understand how modern cricket works, nor do we wish to embrace it.
— Imy (@PakCricket_) December 10, 2024
So ironic to hear, on comms, Saim getting criticized and Rizwan getting praised.
— Kamran Muzaffer (@krick3r) December 10, 2024
You're either part of the problem or part of the solution. Quite a few with mic in hand are a part of the problem - that too with an accent and ill timed giggles.
Babar and Rizwan may have worked in 2021, however the T20 game has evolved since then, such a shame Pakistan’s thinking hasn’t.
— AmerCric 🏏 ✍️ (@Amermalik12) December 10, 2024
Follow Wisden for all cricket updates, including live scores, match stats, quizzes and more. Stay up to date with the latest cricket news, player updates, team standings, match highlights, video analysis and live match odds.
