Kaif Called Axar 'Immature' for Naming Kuldeep — Then DC Dropped Him Anyway
The captain publicly blamed his spinner. The pundits publicly blamed the captain. And then Delhi Capitals benched Kuldeep Yadav for a must-win game — and won. The autopsy of IPL 2026's most painful individual collapse.
The Captain Said the Quiet Part Out Loud
After Delhi Capitals' loss to Chennai Super Kings on May 5, Axar Patel did something captains are trained never to do. He named a teammate. Not in praise. Not in consolation. In regret.
"In bowling, I missed my partner Kuldeep." Six words that landed like a grenade in the DC dressing room. Axar had taken 1/25 in his four overs that night. Kuldeep had gone for 34 runs in three wicketless overs. The implication was surgical: I did my job. He didn't do his.
The comment was technically accurate. It was also, as former India batter Mohammad Kaif would put it within days, spectacularly immature.
A mature captain never publicly takes the name of one of his players or lets his player down. He does not openly blame him. You should never take a player's name publicly. Instead, you should simply say that things did not go well as a team.Mohammad Kaif, on Axar Patel's post-match comments
The Numbers Behind the Naming
Kaif was right about the principle. But the numbers were screaming from Axar's side. Kuldeep Yadav's IPL 2026 has been a slow-motion unravelling — the kind of season where every stat feels like a new layer of humiliation.
Seven wickets in 11 matches. An economy rate of 10.67 — of all bowlers to have sent down at least 30 overs in IPL 2026, only T Natarajan (who bowls at the death) has leaked runs faster. Against KKR alone, Kuldeep was hit for five sixes in three overs — two off short balls, three off full ones, four by Finn Allen and one by Cameron Green.
The most damning number: batters have scored 178 runs off Kuldeep's 70 full-length deliveries this season at a strike rate of 254.28. That's up from 133.65 last season. His stock ball — the full, flighted wrist-spin delivery that made him India's premier white-ball spinner — has become his biggest liability.
Kuldeep Yadav's IPL Decline
| Metric | IPL 2025 | IPL 2026 |
| Wickets | Season contributor | 7 in 11 matches |
| Economy Rate | — | 10.67 |
| Average | — | 50.29 |
| SR off Full Deliveries | 133.65 | 254.28 |
| Wickets off Full Balls | — | Just 2 all season |
The Expert Autopsy
On ESPNcricinfo's TimeOut show, Deep Dasgupta tried to diagnose the technical breakdown. His observation cut to the core of the confusion in Kuldeep's bowling: he's getting hit everywhere, with no pattern to the punishment.
My thing with Kuldeep is that you can't be hit for six over square leg off a short ball, and over long-off and long on as well.Deep Dasgupta, ESPNcricinfo TimeOut
World Cup Fatigue or IPL Funk?
Dasgupta's point is that Kuldeep has lost control of both his lengths and his lines — too many deliveries drifting into that comfortable arc between fourth and eighth stump, the "hand-freeing zone" where T20 batters don't need to think. He can't go short because he gets pulled. He can't go full because he gets driven. He's stuck in no-man's land, and every batter in the IPL knows it.
Former India pacer L Balaji offered a different, more sympathetic diagnosis ahead of DC's match against PBKS: fatigue. Not just physical fatigue — the accumulated mental weight of a T20 World Cup campaign followed by a gruelling IPL season.
Irfan Pathan, meanwhile, aimed his critique not at Kuldeep's body or mind but at the organisation around him. DC's decision-making, Pathan argued, had crumbled under pressure — from team selection to field placements to the way Kuldeep was being used. When a spinner of Kuldeep's calibre goes 11 matches without finding his rhythm, the conversation has to extend beyond the individual.
Kuldeep Yadav is probably fatigued after the T20 World Cup. Wickets in the middle overs are too important in modern-day T20 cricket, and that has been missing with DC because of Kuldeep's form.L Balaji, ahead of PBKS vs DC
The Axe Falls — and DC Win
On May 11, Delhi Capitals made the call that had been building for weeks. Kuldeep Yadav was dropped for the must-win clash against Punjab Kings in Dharamshala — one of five changes DC made to their XI. Auqib Nabi came in as his replacement. Lockie Ferguson was also left out.
The official explanation cited conditions: a fresh Dharamshala wicket that would help fast bowlers early. The real explanation was written in 11 matches of data. Badani had said he would "rally around" Kuldeep on May 5. Six days later, the rallying was over.
And then the cruellest twist: DC won. They chased down 211 with an over to spare, with Axar Patel (56 off 30) and David Miller (51 off 28) leading the charge. For the first time in weeks, DC looked like a team with genuine playoff intent — and they did it without their most expensive spinner on the field.
The Question That Haunts Delhi's Season
Here's the uncomfortable truth that neither Kaif's criticism nor Axar's frustration fully addresses: Kuldeep Yadav was supposed to be Delhi Capitals' trump card this season. The left-arm wrist spinner who bamboozled the best in the T20 World Cup, who had become India's most reliable wicket-taker in the middle overs, who was meant to be the difference between DC's perennial also-ran status and a genuine title push.
Instead, he delivered 7 wickets at an average of 50 and an economy that would embarrass most death bowlers. His captain publicly blamed him. His coach publicly backed him. The experts dissected him. And then the team dropped him — and immediately looked better for it.
Kaif was right that Axar shouldn't have named Kuldeep publicly. But Axar was right that something was deeply, visibly wrong. The saddest part of this story isn't the criticism or the dropping. It's that India's best white-ball spinner spent an entire IPL season searching for the pitch of a ball he used to land in his sleep — and never found it.
Want data-backed predictions for every IPL 2026 match?