Axar 'Cannot Understand' — But 75 All Out Needs No Translation

"I still cannot understand what happened. That is why they say you have to be on your toes at all times in cricket." That was Axar Patel at the post-match press conference on Sunday night. Here's the thing, Axar — the scorecard understood perfectly. 13 for 6 in the powerplay. Six batters back in the pavilion before the field restrictions were even lifted. 75 all out in 16.3 overs. This wasn't a cricketing mystery. This was a public execution.

What "happened" was that Josh Hazlewood and Bhuvneshwar Kumar decided to bowl like it was a Test match in Hobart, not a T20 at the Arun Jaitley Stadium. And Delhi's batters — a lineup that includes KL Rahul, the man who scored 152 just four days earlier against Punjab Kings — responded by playing as if they'd never seen a swinging delivery before. Six wickets in six overs. Thirteen runs. Not a single batter managing to look settled, let alone dangerous.

When the captain says he cannot understand what happened, one of two things is true: either he genuinely doesn't know, which is a problem, or he knows exactly what happened and doesn't want to say it on camera. Either way, Delhi Capitals have a crisis that extends well beyond one bad night.

Let's put 13 for 6 in context. The previous lowest powerplay score in IPL history was 14/2 by Rajasthan Royals against RCB back in 2009, in Cape Town. DC didn't just break that record — they obliterated it. They lost three times as many wickets while scoring one run fewer. In a format designed for aggression, Delhi's top six combined for 13 runs. That's not a collapse. That's a surrender.

Hazlewood set the tone with the new ball, getting the delivery to nip back and move away at will. Bhuvneshwar Kumar operated at the other end with the surgical precision of a man who has been doing this for 15 years — and doing it better than most. The pair shared seven wickets between them: Hazlewood finishing with 4/12 from 3.3 overs, Bhuvneshwar with 3/5 from three overs. Between them, they conceded 17 runs and took seven wickets. That's not a spell. That's a statement.

The pitch played a role — there was enough in it for the seamers early on, as Delhi conditions in late April often offer. But this wasn't a minefield. RCB chased 76 in 6.3 overs without breaking a sweat. This was about the quality of the bowling meeting the fragility of the batting, and the result was one of the most lopsided matches in IPL history.

In the 10th over, Delhi got the kind of divine intervention they desperately needed: a dust storm rolled through the capital, forcing play to stop as the sky turned orange and visibility dropped to near-zero. Players retreated to the sides, shielding their faces from the abrasive winds. For a few surreal minutes, the Arun Jaitley Stadium looked like a scene from Mad Max rather than a cricket ground.

When play resumed, nothing changed. DC were already 13/6, well past the point of no return. Abishek Porel waged a solitary battle, scratching his way to 30 off 33 balls — a knock that, on any other day, would be unremarkable but here represented the only sign that Delhi Capitals employed professional cricketers. David Miller chipped in with 19 and Kyle Jamieson added 12 before the innings mercifully ended at 75.

The real storm wasn't the weather. It was Hazlewood finding late movement at pace and Bhuvneshwar seaming the ball as though it was on a string. Delhi's batters looked like they were playing a different sport entirely — one that didn't involve hitting a cricket ball.

There was a subplot buried under the rubble of DC's innings: Virat Kohli needed 11 runs to become the first player in IPL history to reach 9000 runs. He got them in 15 balls. A few boundaries, a couple of trademark drives, and then two clean sixes off T. Natarajan to finish the match. The chase lasted 6.3 overs. The celebrations lasted longer than the innings.

Nine thousand runs in T20 franchise cricket for a single franchise. That's not a milestone — that's a monument. Since 2008, through lean patches and golden eras, through two RCB coaching staffs and three different captains, Kohli has been the one constant. And he reached this landmark in the most Kohli way possible: against his hometown team, at his hometown ground, with the match over before most fans had finished their first beer.

The only blemish? DC's collapse meant the achievement felt almost anticlimactic. When you're chasing 76, there's no room for a dramatic fifty. Kohli's 23 not out was enough to seal the game, seal the record, and deny Delhi any last shred of dignity. The King of IPL cricket didn't need a throne room — a dust-swept outfield and a 6.3-over chase sufficed.

Every time Bhuvneshwar Kumar produces a spell like this, the same debate resurfaces: should he be on the plane for India's next assignment? At 36, with figures of 3/5 against a lineup featuring KL Rahul and David Miller, Bhuvneshwar isn't just participating in IPL 2026 — he's dominating it. His spell earned him the Purple Cap, making him the tournament's leading wicket-taker.

Former India batter Mohammad Kaif has already made his position clear earlier this season: "Bhuvi still has it in him." And on the evidence of Sunday night, it's hard to argue. The economy of 1.67 isn't just elite for T20 cricket — it's elite for any format. The control, the movement off the seam, the ability to make top-order batters look like they've never faced pace bowling before — at 36, Bhuvneshwar is bowling the best cricket of his late career.

Whether India's selectors agree is another matter. But Hazlewood, who himself took 4/12 and became the first overseas player to reach 50 IPL wickets for RCB in this match, would have been the first to acknowledge that Bhuvneshwar was the more threatening of the two. When a bowler makes a score of 5 runs in 3 overs look like generosity, the conversation shifts from "should he play?" to "can you afford not to pick him?"

Here's where it gets brutal for DC fans. This was their fourth loss in eight matches, leaving them with 3 wins and 5 losses. In a 14-game season, that's deep trouble. The net run rate damage from a 9-wicket loss chased down in 6.3 overs is catastrophic — it's the kind of NRR hit that eliminates you even if you win your remaining games.

Four days ago, KL Rahul was scoring 152 off 67 balls against PBKS in a match where DC posted 264 and still lost — the highest-ever successful chase in IPL history. Now the same team has been bowled out for 75. That's a swing of 189 runs in four days. That's not inconsistency. That's incoherence. One performance belongs to a team challenging for the title. The other belongs to a team that should be questioning whether it has the temperament to compete in franchise cricket.

Axar Patel said he "cannot understand what happened." With all due respect to the DC captain: 75 all out, 13/6 in the powerplay, bowled out in 16.3 overs, match over in under 90 minutes, season in intensive care. If that needs explaining, the problem runs deeper than one bad night in Delhi.