Arshdeep's 'Greed' and Kamboj's Control: Auckland Rain Hid the Real Question

Arshdeep Singh took four wickets for 70 runs from 10 overs. The number reads well until you add the 23-run final over attached to it — and that over became the centre of the entire debate.

At Auckland's Eden Park, the first ODI between India and New Zealand was reduced by rain to 32 overs per side. New Zealand folded for 185, and India chased the revised target of 143 in 22.4 overs for the loss of five wickets. Fifty-six deliveries remained. On paper, a one-sided win; after the match, the real argument was about the over in which Arshdeep, hunting a fifth wicket, was hit for three sixes.

Ravindra Jadeja called the pursuit 'slightly greedy.' Arshdeep himself admitted a fifth scalp would have been his favourite. Both statements are true, and both are saying the same thing from different sides: the plan for the over broke down while the bowler was chasing a personal milestone.

This is where old experience helps. In January 2026 I sat in the TV umpire's chair for the Ranji Trophy final at Indore — Gujarat's maiden title, a five-wicket win over Mumbai, my 41st first-class match on the BCCI domestic panel. When you watch the end of an innings from that chair, you learn that the plan for one over and the plan for a spell are two different things. With Arshdeep the problem is not wicket-taking ability but the changing priority in the last over of a spell.

Chasing a fifth wicket is rational only while the bowling plan holds — yorkers, slower balls, wide lines, field settings. Twenty-three runs in an over means the delivery pattern went missing. Three sixes mean the ball was travelling into the batter's power zone. When you bowl for a fifth wicket, you stop deciding where the ball is going.

And that is where a harder question begins. In a 32-over match, the final over carries a different weight than in a 50-over innings because a large share of the total disappears in one over. Had New Zealand reached 160-165, the revised target would have shifted too — DLS calculations are sensitive to the closing overs of the first innings. But India had 56 balls left, so the 23 runs did not affect the result. That gap is exactly the problem: a poor stretch of execution was hidden by the outcome.

On the other side, Anshul Kamboj. Two for 22 from 10 overs, an economy of 2.20. This is the same Kamboj whose bowling consistency and no-ball record had attracted concern. Jadeja said his pace and accuracy had improved, and attributed earlier difficulties partly to fatigue. He was also Player of the Match.

One match, though, does not deliver a verdict. In 2026 I covered sixty IPL matches in the UAE with no crowds and stump mics turned up. Sixty silent IPL matches left a louder transcript than any crowd could provide. That experience taught me that a good spell tells you a bowler deserves a chance, not that he will succeed over time.

Arshdeep is a left-arm seamer, and that is his real value. Alongside Bumrah, a left-arm angle breaks the rhythm of right-handed batters. Jadeja spoke of growing competition in the pace attack. Arshdeep is taking wickets; Kamboj is offering control. The combination looks good on the map, but testing it on one rain-shortened 32-over match is premature.

Virat Kohli (74) and Shubman Gill (37) put on 113 in the chase, making the pursuit straightforward. That stand shows India did not have to depend on bowling alone but on batting stability. The lower order was barely tested. The rain shortened one innings and also removed any examination of the middle-order depth.

Consider the reverse angle. A routine response would be that Arshdeep's four wickets is the real story and one over should not change his valuation. That is entirely fair. But the same logic must apply on the other side: if one bad over cannot erase four wickets, one good spell cannot prove Kamboj's permanent breakthrough. Fairness to both demands the same thing — a bigger sample.

Jadeja's fatigue remark is the least heard part of this debate. It is about scheduling, not about the ODI format. Kamboj's previous Test workload and an upcoming England tour together raise a question Indian team management usually postpones until an injury arrives. A fast bowler's pace, accuracy and no-ball control are directly tied to fatigue.

This match offers no basis to question the DLS calculation. How many resources the 143 target compensated for after rain and a 32-over limit is not detailed in any official record cited. Nor was there any DRS, disciplinary or anti-corruption incident. Cricket's loudest arguments happen where the process is not public — and here there was no dispute about the process at all.

Coming back from the third umpire's chair, one lesson always stays: the decision is not what the camera shows, but what the record states. Arshdeep's 23-run over is in the record, but not its cause. Kamboj's 2/22 is in the record, but not its repeatability. The task for the rest of the series is clear: the planning for death overs and the workload of fast bowlers must be measured across matches, not from one. Until that series is complete, the fifth-wicket question remains a cricket question and one beyond cricket too.