The truth behind Babar Azam’s underwhelming stint with Sydney Sixers
By Nawaz Gohar ; Babar Azam’s performance on Australian tracks has ignited a firestorm of debate, raising serious questions about his form and adaptability in modern T20 cricket.
His sudden departure from the Sydney Sixers just before their high-stakes Challenger match, was it merely a coincidence, or the boiling point of immense performance pressure? Babar’s stint in this BBL season was nothing short of a nightmare.
What began as criticism over a sluggish strike rate quickly evolved into a struggle for big scores, and finally peaked with the infamous “single-run” controversy involving Steve Smith.
The tension became palpable when Smith denied him a run to keep the strike, sparking a visible display of frustration from the Pakistani star and fueling rumors of a rift within the Sixers’ camp.
The Alarming Numbers Babar’s statistics tell a worrying story of a player out of rhythm in a league that demands relentless aggression:
Matches: 11 | Runs: 202
Boundaries: 19 Fours & 3 Sixes
Strike Rate: 103.06
Low Scores: Failed to reach double figures in 7 innings.
In a tournament where top-tier batters are operating at strike rates between 150 and 200, Babar’s inability to accelerate remained a glaring weakness. In nearly half of his outings (5 out of 11), he failed to even cross the 2-run mark, putting undue pressure on the Sixers’ top order.
While Babar and the Sydney Sixers have officially parted ways with smiles and “mutual respect,” the optics suggest a more complex reality.
Analysts are now asking: is it truly an “amicable release” for a marquee player struggling for runs, or is it a diplomatic way of dropping a superstar before the most critical games of the season?
