From Karnal to Mullanpur: The Spreadsheet Behind Anshul Kamboj's Debut That Will Outlast the Broadcast

The 31st over in Guwahati. Prasidh Krishna grabbed his hamstring, called for the physio, and the television camera tilted slowly towards his leg. The commentary said, “a big blow for India.” Outside the ground, another line was glowing in my notebook — 5 overs, 45 runs, 1 wicket, economy 9.00. The man being described as a “blow” was, in that match, effectively distributing runs. The wicket of Keacy Carty did arrive, but around it the ball kept flying towards the boundary.

After years of watching cricket, I am used to this scene: the camera shows the injury, the broadcast manufactures drama, and nobody asks the real question. The question is this — why is a 24-year-old pacer from Karnal suddenly being handed the ball? The answer is simple, but not comfortable: this is not planned rotation, it is compulsion. The spreadsheet did not interrupt the broadcast; it simply outlasted it.

According to The Tribune, Anshul Kamboj is set to make his ODI debut in the third and final ODI of the series against West Indies. The match is at the Maharaja Yadavindra Singh PCA International Stadium in Mullanpur, starting at 2 pm. This is the first men’s ODI at the venue — meaning there is no historical database for the pitch, the bounce, or the scoring pattern. Kamboj comes in for Prasidh Krishna, who has been ruled out with a hamstring injury.

Kamboj’s CV is brief but notable. The pacer from Karnal in Haryana has a List A record of 56 wickets in 35 matches at an average of 22.41. He made his Test debut on India’s tour of England last year. Recently, playing for India A against Australia A, he took three wickets in the first match and left the squad after bowling two overs in the second innings to link up with the national team. His debut cap was handed to him by Virat Kohli himself.

What the report does not say matters too: the series score, the pitch report, the toss result, the weather and dew forecast, the DLS risk — none of it is mentioned. Those gaps are the real field of analysis.

The tactical context of ODI cricket

In 50-over cricket two new balls are used, so the first ten overs offer pacers their biggest window. Spinners control the middle overs, and the attack returns in the final ten. Where a new pacer fits in that rhythm depends on his type of bowling — new-ball swing, or death-over control.

Kamboj is being viewed as a replacement for Prasidh Krishna, meaning a similar workload. But the report gives no economy rate, no strike rate, no phase-based splits. So how suitable he is for that role cannot be proven with data — only suggested.

The List A average of 22.41: strong, but not an international certificate

In modern ODI cricket, a pacer’s average below 25 is good, and below 20 is elite. So 22.41 is a firm number. But it is List A, not international ODI. Thirty-five matches is a moderate sample — not a long career, but an indication of a trend.

The bigger gap is that the report gives no economy rate, no strike rate, no new-ball versus death-over split, and no split against left-hand and right-hand batters. Without that information we cannot tell who Kamboj is — an attacking new-ball wicket-taker, or a middle-overs run-checker. In ODI cricket those two roles demand entirely different plans.

There is another limit to a List A average — the Indian domestic environment. Familiar pitches, a familiar ball, occasionally weaker opposition. In those conditions a good average is easier to produce. Without knowing how the number holds up away from home or at international level, 22.41 cannot be treated as proof of ODI readiness.

Here one big caution is essential: formats must not be mixed. List A and Test data are not direct ODI evidence. Kamboj’s Test debut may say something about his temperament, but it says nothing about his white-ball economy or his death-over capability.

What the pathway says: a multi-format signal

The strongest evidence for Kamboj’s selection is twofold — his List A record and his recent India A opportunity. A Test debut on the England tour means the selectors do not see him merely as a T20 specialist; they also see him as a red-ball project.

He left the Australia A side after bowling two overs in the second innings. That is not an injury signal, but a logistical decision — to join the national team. The report does not explicitly state that he is fully fit, however. The uncertainty is small, but it should not be ignored.

One feature of the Indian domestic pathway is also worth remembering. Pacers who emerge from states like Haryana often grow up on hard pitches, which helps them develop bounce and pace. But proving consistency with limited opportunities is hard. Kamboj’s 35 matches sit exactly on that boundary line.

Age 24: the workload calculation

Pace bowlers usually mature between 24 and 30. At 24 he is still in a development phase, but it is precisely at this age that workload management matters most.

The biggest risk is a sudden change. He is coming straight from red-ball and India A commitments into an ODI debut — a different ball, a different rhythm, a different mental load. That kind of jump can leave long-term effects on a fast bowler’s body. Prasidh Krishna’s hamstring injury is itself a reminder of that risk environment.

Mullanpur: a venue with no data

This is the real darkness in the analysis. No men’s ODI history means there is no basis for how the pitch will behave, how much spin will grip, whether dew will fall in the evening, or what a “safe” first-innings score is.

A 2 pm start offers one clue: the game will stretch into the evening, and dew in the second innings can ruin a bowler’s grip. If rain arrives, the DLS calculation also becomes unpredictable. No team is arriving with experience at this venue, so the uncertainty is equal for both.

A new venue can mean a high-scoring surface or a slow, spin-friendly one — both are possible. But that is the difference between assumption and evidence: we have assumptions, not information.

The data gap and the duty of verification

The Tribune is a reliable mainstream outlet, but it is a single source. It is not a specialist cricket data provider. So figures like Kamboj’s List A average or the details of Prasidh’s spell should be cross-checked against ESPNcricinfo, Cricbuzz, or official ICC data.

Verifying from outside India makes this more important. Where cricket-data culture is deep, an average becomes a debate; where it is thin, the same number becomes a certificate. Filling that gap is the analyst’s duty, not the broadcaster’s.

The role: who will Kamboj be?

What can be inferred from the report is that he will come into the XI as a pace option like Prasidh — though that is not certain until the toss or the team announcement.

One question stays open: will India give him a protected spell, or a full ODI workload? Since the series score is not known, it is impossible to tell whether the match is a dead rubber or a decider. If it is a dead rubber, the selectors will probably give him the full ten overs as a test.

What the viewer sees

An ordinary viewer sees a debut as a story — a boy fulfilling a dream. That story is true, but incomplete. Behind it sit data gaps, injury pressure, and the total uncertainty of a venue. For the fan who watches every match, the real question is different — is the team building for the future, or filling today’s hole?

The trap of easy inference

The easiest thing is to treat 22.41 as a certificate of success. But correlation is not causation. A direct line cannot be drawn from a good List A average to a successful ODI debut — between them sit the type of ball, the field, the pressure, and the quality of the opposition.

Another trap is the single-match sample. Prasidh’s spell of 5-0-45-1 is a snapshot of one match; it cannot be used to judge his overall ability. Equally, Kamboj’s three wickets against Australia A are the story of one match — not international proof.

One point deserves to be stated separately. Receiving the debut cap from Virat Kohli is a signal of emotion and symbolic acceptance, but it is not performance data. The broadcast will show that moment; the spreadsheet will not. Data never shouts; it waits, and in the end it lasts.

The biggest counter-intuitive truth is this: this debut is not really Kamboj’s story. It is the story of India’s pace depth. One pacer’s hamstring means international responsibility lands directly on an untested 24-year-old — and that thread tells us depth is not as deep as it looks. The broadcast does not show that thread, because it does not form in a single day.

What to watch next

At Mullanpur, the eye should be on role, not runs. Whether he finds swing or seam movement in the first spell, whether he can check runs in the middle overs, whether he uses the yorker and the slower ball correctly in the final ten — the answers to those three questions will decide whether this is a one-day trial or the start of a longer plan.

Watch the workload too. If he bowls his ten overs and holds his rhythm to the end, that is real evidence of a transition from red ball to white ball. If he breaks down midway, questions will arise about the continuity of his preparation.

One thing must not be forgotten: nobody builds a career on one innings, and nobody is dropped on one innings either. The Mullanpur pitch will not give a certificate, only a signal. The question is whether we read that signal through the broadcast’s eye, or the spreadsheet’s.