Axar Patel’s decision not to step up and prevent Abhishek Sharma from plundering his bowlers cost Delhi Capitals dearly in match 31 of IPL 2026. Abhishek brought up his first century of the season as he pulverised Delhi’s bowling attack. The southpaw batted at a strike rate of 198.52, smashing 10 fours and as many sixes during his unbeaten 135 off just 68 balls.
Abhishek’s captivating century guided Sunrisers Hyderabad (SRH) to 242, and Delhi got buried under its weight. Delhi eventually lost by 47 runs, but a change in strategy could have saved them from such an onslaught.
Did Axar Patel’s reluctance to bowl to Abhishek Sharma cost DC?
Delhi’s captain Axar Patel bowled only two overs in the game. He deliberately held himself back as he thought that, as a left-arm spinner, turning the ball into Abhishek’s hitting arc was a favourable match-up for the SRH opener and one that he (Axar) was bound to lose.
While Axar can’t be entirely blamed for making that call. Match-ups have become a thing in modern-day cricket. They hold paramount significance and influence the strategies of teams. However, Axar ignored his favourable head-to-head record against Abhishek in doing so. The Delhi Capitals captain had dismissed Abhishek twice in eight balls for just six runs before the game.
In fact, it was Axar who broke the 97-run stand between Abhishek and Travis Head by dismissing the Aussie in the ninth over. But as Abhishek continued to inflict carnage on the Delhi Capitals, Axar never brought himself into the attack again.
Axar’s reluctance to reintroduce himself underlined his belief in match-ups and his lack of self-belief. But his worst nightmare came to life anyway as Abhishek remained unbeaten and batted Delhi out of the game.
While there’s no guarantee that Axar would have dismissed Abhishek as he dismissed Head had he given himself that option, not even considering the move certainly made Abhishek’s job easier and cost Delhi two valuable points.
