Arshdeep's Fifth-Wicket Chase: Auditing One Over, and Why Kamboj's 2/22 Is the Bigger Question

Before I opened the ball-by-ball sheet for Eden Park, Auckland, I wrote two numbers at the top of the card — Arshdeep Singh 10-0-70-4, and Anshul Kamboj 10-0-22-2. The first tells you four wickets; the second tells you an economy of 2.20. But overs are not read in that order. Arshdeep's final over cost 23 — three sixes, and a chase for a fifth wicket that never arrived. In a rain-reduced 32-over fixture, India bowled New Zealand out for 185 and then chased a revised 143 in 22.4 overs, five wickets in hand, 56 balls to spare. Virat Kohli made 74, Shubman Gill 37, and their 113-run stand put the chase to bed. The whole match, in the record, folds into that one over. What I am auditing here is whether those 23 runs were an accident, or the last unchecked point in a process.

The rain structure has to be understood first, because a 32-over ODI is not the 50-over game whose statistics we have learned by heart. The innings split into two segments — the ten-over powerplay where the new ball and a fast outfield raise the price of wickets, and the closing six to eight where every run-rate recalculation can flip the target. When you have 32 overs rather than 50, the final over carries weight far beyond its one-thirty-second share of the innings. In a revised-target game, the runs conceded after that over feed directly into the Duckworth-Lewis-Stern resource percentage. The report gives 143 as the target but not the overs lost, the interruption timeline, or the DLS percentage. I will stop and note that in my copy, every figure that came off a broadcast graphic sits in a different colour of ink — and the arithmetic behind 143 is not in my possession, so I will quote it as 'reported'. Nor did a pitch report reach me, so venue-specific conclusions would be dishonest. For me, the story of this match is not the pitch; it is the bowlers' workload blocks.

Arshdeep's spell has to be read the way a controller reads the ledger. Ten overs, 70 runs, four wickets. Take out the last over and he was 4/47 — hugely effective, expensive by run-rate, and worth far more than the raw economy suggests. Had he conceded eight or nine in the last, the card reads something like 4/55, which in this context is excellent for a left-arm seamer. Instead he conceded 23, three sixes in it. Ravindra Jadeja called the pursuit of a fifth wicket 'slightly greedy'. That word needs weighing. Chasing a fifth wicket is not a technical failure; it is a procedural deviation — the over's objective shifts from 'stop runs' to 'take a wicket,' and the second becomes the primary. Arshdeep said afterwards a fifth would have been his favourite, and that human admission is the clearest clue to his delivery mix. In a 32-over game with nothing left to chase, you go for the top of the bat — short ball, yorker versus wide yorker, slower ball versus pace, choices that matter more than the field setting. The report gives no field placement, no delivery type and no bowling plan, so my diagnosis is procedural, not technical.

And here is the real contrarian point, the place where I think the outside reading is wrong. On the same night Arshdeep's last six balls went for 23, another bowler took 2/22 from ten overs and won Player of the Match. Kamboj's spell is the kind of entry that vanishes from a report because it sat quietly beside the loud over. In a 32-over match, a bowler conceding 22 changes the shape of the opposition: it prevents partnerships forming after the powerplay, it spares the captain from asking for another quick's overs, and it keeps the field the same. But I will not fall into the trap of calling one excellent spell a breakthrough. One innings in a 32-over game is not 12 months of progress. Jadeja linked Kamboj's earlier difficulties partly to fatigue — the kind of information the scorecard does not hold. The report says his pace, consistency and accuracy improved. For me the question is whether that was match-level adaptation or a system-level correction. Only the five-match series and the no-ball count will answer that, and until those two checkpoints are cleared I will not write 'improvement' in my file under today's date.

Now the part where I disagree with the read. The main coverage framed this match as 'Arshdeep's chase for a fifth wicket' — headlines off the 23-run over, four wickets in the footnote. I read it the other way. The most important fact is how the 185 was built: India bought both wickets and control from Arshdeep's first nine overs and Kamboj's ten. Kohli and Gill's 113-run stand made the target so simple that India's chase rate was about 6.31 an over — 143 in 22.4 overs, meaning sustained control, not a late rescue. Fifty-six balls to spare is the signal that this was not a cliffhanger. And here I acknowledge the limit of my method: I was not in Auckland. I have the broadcast feed, the wire report and the scorecard. Every ground-level detail I write, I will name its source.

The 'greed' framing Jadeja's quote put into the air is a high-visibility media construct — and I treat it as his assessment, not a verdict. A four-wicket haul does not mean the last over is beyond debate; it means the team needs a terminal-over protocol that separates the chase for the wicket from the winning of the match. I think chasing a fifth when you already have four is legitimate. But in a 32-over format, the last over's context changes completely — every run's proportion inflates. It is the Repino lesson: a set piece is a ledger with legs, and you have to watch it move. A bowling plan is the same ledger.

I think the real signal from this match is hidden in the next one, not in the last scorecard. India won the first ODI in New Zealand, and if the fast-bowling depth is growing — a left-arm angle from Arshdeep, control from Kamboj, and Bumrah's presence — the question is whether the combination can be repeated. Two lines in my ledger stay open: one for Arshdeep's final over, which I will track every spell to see whether the urge for a fourth wicket costs him his economy each time; and one for Kamboj's no-ball, whose real test arrives across five matches. Until those checkpoints are cleared, I will call this a controlled win by five wickets and 56 balls — not the story behind a bowler's fifth wicket. The series is still open.