T20 World Cup: Mohammad Kaif's blunt live-TV take on Babar Azam goes viral
Pakistan secured a narrow three-wicket win over the Netherlands in their T20 World Cup opener. Babar Azam's slow batting tempo has sparked intense debate about his role in the modern T20 format.
Pakistan may have escaped with a three-wicket victory in their T20 World Cup 2026 opener against the Netherlands, but the post-match discourse has been dominated by a familiar shadow: the batting tempo of Babar Azam. Despite a flawless day on the field, Babar’s laboured 15 off 18 balls has reignited a fierce debate over his suitability for the modern T20 game, especially after a dramatic middle-order collapse nearly handed the Dutch a historic upset.
Former India cricketer Mohammad Kaif's blunt take on Babar's inability to accelerate has gone viral on social media.
"Hitting sixes isn’t his strength. You said he would hit a six. Yes, he tried, but look what happened, he got out. His style isn’t about hitting sixes; he doesn’t have that kind of power," he said on-air while doing commentary in Hindi language for the official broadcasters.
Under the scorching Colombo sun at the Sinhalese Sports Club (SSC) on Saturday, February 7, Pakistan initially looked every bit the "tidy" outfit fans had hoped for. After skipper Salman Ali Agha opted to bowl, the Pakistan attack—led by Salman Mirza’s 3 for 24—restricted the Netherlands to 147 all out. Babar himself was the star of the first innings, pulling off a breathtaking relay catch with Shaheen Afridi to dismiss Michael Levitt, setting a high bar for fielding standards.
However, the chase proved far from straightforward. While Sahibzada Farhan (47 off 31) provided a blistering start to take Pakistan to 98 for 2, the entry of Babar Azam saw the momentum screech to a halt. Between the 10th and 15th overs, Pakistan managed a measly 21 runs.
Babar’s inability to find the boundary—coupled with a boundary drought of 29 deliveries—piled immense pressure on the other end.
When Babar eventually holed out to long-off for 15 (with a strike rate of 83), it triggered a typical Pakistan collapse. The Men in Green slumped from 98 for 2 to a precarious 114 for 7, leaving the Dutch scenting blood. It took a heroic, unbeaten 29 off 11 balls from Faheem Ashraf, including a 24-run onslaught in the 19th over, to drag Pakistan across the finish line with just three balls to spare.
The backlash was immediate. On social media and in the commentary box, analysts questioned why a veteran of Babar’s stature struggled to rotate strike against an Associate nation’s spin attack.
IS BABAR NOT SUITED FOR T20Is?
Many have argued that Babar’s anchor role is increasingly becoming a tether, one that drags the team down rather than holding it together. In a chase where the required rate hovered at barely seven an over, his 18-ball stay drained momentum, forcing the lower order into high-risk strokes that nearly turned the game into a catastrophe.
Babar was dropped from Pakistan’s T20 setup after Mike Hesson took over as head coach last year. He was, however, recalled ahead of the T20 World Cup, even as the former captain continued to struggle to assert himself in the shortest format.
Since the start of 2025, Babar has scored 297 runs in 12 matches at a strike rate of 114.67. His maiden stint in the Big Bash League only deepened concerns, yielding 202 runs from 11 matches at a strike rate of 103.06. Babar’s limitations in power-hitting were laid bare during his time with the Sydney Sixers, most notably when Steve Smith repeatedly denied him the strike in a telling moment of tactical distrust.
WHAT DID PAK CAPTAIN SAY?
While fans voiced their frustration, captain Salman Ali Agha remained protective of his predecessor, attributing the tension to the pitch conditions. "We did it the hard way," Salman admitted during the post-match ceremony. "The pitch was holding a bit, and we lost our way in the middle, but the important thing is we have the two points."
With a self-imposed boycott of their scheduled clash against India looming, Pakistan has zero margin for error. If Babar Azam cannot find his "fifth gear" soon, the "clinical" era Pakistan promised may be over before it truly begins.
Pakistan may have escaped with a three-wicket victory in their T20 World Cup 2026 opener against the Netherlands, but the post-match discourse has been dominated by a familiar shadow: the batting tempo of Babar Azam. Despite a flawless day on the field, Babar’s laboured 15 off 18 balls has reignited a fierce debate over his suitability for the modern T20 game, especially after a dramatic middle-order collapse nearly handed the Dutch a historic upset.
Former India cricketer Mohammad Kaif's blunt take on Babar's inability to accelerate has gone viral on social media.
"Hitting sixes isn’t his strength. You said he would hit a six. Yes, he tried, but look what happened, he got out. His style isn’t about hitting sixes; he doesn’t have that kind of power," he said on-air while doing commentary in Hindi language for the official broadcasters.
Under the scorching Colombo sun at the Sinhalese Sports Club (SSC) on Saturday, February 7, Pakistan initially looked every bit the "tidy" outfit fans had hoped for. After skipper Salman Ali Agha opted to bowl, the Pakistan attack—led by Salman Mirza’s 3 for 24—restricted the Netherlands to 147 all out. Babar himself was the star of the first innings, pulling off a breathtaking relay catch with Shaheen Afridi to dismiss Michael Levitt, setting a high bar for fielding standards.
However, the chase proved far from straightforward. While Sahibzada Farhan (47 off 31) provided a blistering start to take Pakistan to 98 for 2, the entry of Babar Azam saw the momentum screech to a halt. Between the 10th and 15th overs, Pakistan managed a measly 21 runs.
Babar’s inability to find the boundary—coupled with a boundary drought of 29 deliveries—piled immense pressure on the other end.
When Babar eventually holed out to long-off for 15 (with a strike rate of 83), it triggered a typical Pakistan collapse. The Men in Green slumped from 98 for 2 to a precarious 114 for 7, leaving the Dutch scenting blood. It took a heroic, unbeaten 29 off 11 balls from Faheem Ashraf, including a 24-run onslaught in the 19th over, to drag Pakistan across the finish line with just three balls to spare.
The backlash was immediate. On social media and in the commentary box, analysts questioned why a veteran of Babar’s stature struggled to rotate strike against an Associate nation’s spin attack.
IS BABAR NOT SUITED FOR T20Is?
Many have argued that Babar’s anchor role is increasingly becoming a tether, one that drags the team down rather than holding it together. In a chase where the required rate hovered at barely seven an over, his 18-ball stay drained momentum, forcing the lower order into high-risk strokes that nearly turned the game into a catastrophe.
Babar was dropped from Pakistan’s T20 setup after Mike Hesson took over as head coach last year. He was, however, recalled ahead of the T20 World Cup, even as the former captain continued to struggle to assert himself in the shortest format.
Since the start of 2025, Babar has scored 297 runs in 12 matches at a strike rate of 114.67. His maiden stint in the Big Bash League only deepened concerns, yielding 202 runs from 11 matches at a strike rate of 103.06. Babar’s limitations in power-hitting were laid bare during his time with the Sydney Sixers, most notably when Steve Smith repeatedly denied him the strike in a telling moment of tactical distrust.
WHAT DID PAK CAPTAIN SAY?
While fans voiced their frustration, captain Salman Ali Agha remained protective of his predecessor, attributing the tension to the pitch conditions. "We did it the hard way," Salman admitted during the post-match ceremony. "The pitch was holding a bit, and we lost our way in the middle, but the important thing is we have the two points."
With a self-imposed boycott of their scheduled clash against India looming, Pakistan has zero margin for error. If Babar Azam cannot find his "fifth gear" soon, the "clinical" era Pakistan promised may be over before it truly begins.