The Slow Ledger: Kumar Kushagra's 132 Balls, Three Runs and the Shadow of ₹7.2 Crore

Duleep Trophy final, last session of the second day. It was half past eleven at night in Dhaka, a notebook open beside the laptop, and the stream stuttering every four overs. Kumar Kushagra was out for 101 off 132 balls. The partnership with Ishan Kishan had put on 230.

The next morning I checked the numbers again. The first fifty came off 74 balls, the next fifty-one off 58. A strike rate of 76.5. To a T20-conditioned eye that reads as slow. In red-ball cricket it reads as correct — the innings accelerates at the end, and the risk does not rise with it. The next page of the same ledger shows the exact opposite picture. IPL: three innings, three runs.

One hundred and thirty-two balls held together, and three innings yielding three runs, written on facing pages of the same career. The gap between them is not a gap in talent. It is a gap in opportunity. What follows is an attempt to keep that ledger, and to timestamp how far commercial value and sporting value have drifted apart in Indian domestic cricket.

Indian domestic cricket is not one thing. It is at least four structures, and each needs its own accounting. The Ranji Trophy is four-day red-ball work, long innings, session-by-session grind. The Duleep Trophy assembles the best of the zones, where a century carries disproportionate weight. The Vijay Hazare Trophy is fifty-over List A, where average and strike rate both count. The Syed Mushtaq Ali Trophy is the fastest domestic format.

Above all of them sits the IPL, which is not a cricketing structure so much as an economic one layered on top — its own auction, its own valuation logic, its own incentives. That is precisely what makes Kushagra's case instructive. The price at which a 21-year-old was bought on the domestic red-ball stage did not come from his cricketing record. It came from demand.

Kushagra's domestic home is Jharkhand. In the 2026-26 season Jharkhand won the Syed Mushtaq Ali Trophy for the first time, and his contribution to that campaign was 422 runs at a strike rate above 160. That is a team-level data point, and team-level data usually carries more weight than individual data, because it shows the numbers were not merely personal — they won matches.

The opportunity itself did not arrive directly. When Rishabh Pant was injured, a slot opened in the India A side, and the call went to a 21-year-old wicketkeeper-batter. This mechanism is not new in Indian cricket, but it is rarely stated aloud: an injury to a senior is very often what opens the door for the next generation. India A is the second tier of the Indian circuit, and selection there means the name has entered the senior conversation.

But it is worth being precise about what kind of door this is. It is not a door to permanent succession; it is a door to presence. When Pant returns, the door can close. An India A call-up is therefore an opportunity more than an achievement — and opportunities carry expiry dates.

Now the ledger, format by format. One principle first, learned while sitting in Russia: numbers from one format cannot settle a question in another. Red-ball averages do not explain T20 strike rates. Four formats, four separate ledgers.

In first-class cricket the picture is strongest. In the 2026-26 Ranji Trophy he made 572 runs, including a century against Uttar Pradesh. By domestic standards a strong season usually means 700 to 900 runs, so this sits in the medium-to-medium-high band. But the Ranji number read alone misleads, because another line sits beside his name: 266 against Nagaland in the 2026-22 season. In domestic cricket 266 is not merely a big score; it is a conversion innings — proof of the ability to turn a start into something long. That is the rarest skill in red-ball batting.

His recent Duleep Trophy sequence reads 55, 0, 22, 101, 46. That line has a reading rule. There is one large innings, surrounded by moderate scores and a duck. In other words, the floor has not yet been built. Anyone concluding from the 101 alone is wrong; anyone concluding from the 0 alone is equally wrong. The real information is the variance — capable, not yet stable.

The same signature appears in the India A series against Australia at Puducherry: 113, 46 not out, 10, 1. One large score, one unbeaten innings, two failures. The same pattern again — peaks above an unsettled base. And that series was played in India, in familiar conditions. The overseas test had not yet begun.

In List A the numbers are cleaner. At the Vijay Hazare Trophy: 368 runs in seven matches at an average of 73.60 and a strike rate of 102.5. In modern List A cricket an average above 40 is good and a strike rate in the 85-to-95 band is par. Seventy-three point six and 102.5 together represent elite-range numbers inside a small window. The only problem is the window — an average across seven matches is a signal, not a durable truth.

In T20 the picture is the most interesting and the most overlooked. At the Syed Mushtaq Ali Trophy: 422 runs at a strike rate above 160. In the Jharkhand T20 Premier League: 78 off 39 balls (strike rate near 200) and 58 off 26 (near 223). In domestic T20 those are finisher-tier numbers.

Now the IPL column. Bought for ₹7.2 crore at the 2026 auction, with three franchises bidding. The output: three innings, three runs. Then Delhi released him, Gujarat Titans acquired him for considerably less, and he has played once in two seasons.

Placed side by side, one conclusion becomes hard to avoid: a batter who makes 422 runs at a strike rate above 160 in domestic T20 does not produce three runs in three IPL innings because the ability is missing. The reason is a shortage of opportunity and a shortage of adaptation time. 'Insufficient opportunity' and 'insufficient talent' are not the same thing, and domestic cricket analysis conflates them more than almost any other pair of ideas.

The coach's comment is subtle. He said Kushagra has the ability of top-level players, but that it needs to be extended. That is praise, but conditional praise — it names the exact gap that remains. And that gap is visible to a coach more than to a club supporter.

Two training decisions deserve separate attention. First, a deliberate switch to green wickets — manufacturing bowler-friendly conditions and batting on them. Second, a move from the middle order up to No 3.

The green-wicket decision was acknowledged openly: it was done to build comfort in difficult conditions. Batting at No 3 means facing the new ball, meeting the hardest situation early in the match. Read together, these two decisions indicate the preparation is not for a T20 finishing role — it is for red-ball cricket. In the Indian selection structure that is a directional signal, and it is being given at exactly the right age, because batters typically peak between 27 and 33.

One aspect is under-discussed. Kushagra keeps wicket. After a long innings he still has to stand behind the stumps. Keeping is a continuous expenditure of concentration, a continuous draw on physical reserves. Batting at No 3 adds load on top of that expenditure, because No 3 means facing the new ball while the pitch is at its liveliest. Keeping plus batting at No 3 at the age of 21 is the least discussed risk in this case. No scorecard shows it, because fatigue is not a statistic.

Now the place where the common reading goes wrong. Many see three IPL runs and conclude he is not ready. That conclusion is wrong for two reasons.

First, sample size. Three runs in three innings is not a statement about a batter's ability; it is an unfinished sentence. Four hundred and twenty-two domestic T20 runs at a 200-plus strike rate say the opposite. Before choosing between two data points, ask which has more balls behind it. The answer points to the domestic circuit.

Second, the opportunity calculation. In the IPL there are almost no top-order slots for young Indian wicketkeeper-batters. Franchises prioritise proven finishers and overseas batters. In that structure a developing keeper-batter struggles to get matches at all, and without matches a strike rate never develops. The IPL failure here is a structural outcome, not a cricketing verdict.

But I have to stand against my own argument, because the opposite is equally true. 'Slow but steady progress' is a comfortable frame, and comfortable frames are usually incomplete. Its weakness is that it presents domestic success as though conversion to the next level were automatic. It is not. Domestic red-ball runs do not convert automatically into Test runs, and domestic T20 strike rates do not convert automatically into IPL strike rates.

In nine years of watching, the conversion question is the most neglected. I covered eighteen matches in empty stadiums in 2026 for Mohammedan SC, with no sound in the stands at all. There I learned that silence has a possession stat of its own — what is absent also counts. What is absent in Kushagra's case is data from overseas conditions. The 113 at Puducherry came on Indian soil. Playing well at home and playing well abroad are different skills, and the second has no evidence yet.

The second thing the 'slow but steady' framing hides is the nature of the peaks. 266, 101, 113 are excellent numbers, but all three are peaks inside unstable sequences. A batter is defined by the floor, not the ceiling. Kushagra's floor remains unknown, because the sequences read 55, 0, 22, 101, 46. A duck there is uncomfortable but normal; the real issue is the pattern between 22 and 46, where innings begin but do not grow.

In the coach's language, this is the question of extending an innings. And note that the coach did not identify a technical flaw — he named a capacity to bat longer. The problem sits at the level of decision-making, not the angle of the bat. Which ball to leave, how long to stay patient, when to attack: those decisions are the real condition for converting starts into long innings.

Now the commercial side, where the biggest lesson sits. ₹7.2 crore at the 2026 auction, with no IPL track record at the time. What he had was a 266 against Nagaland in the 2026-22 Ranji and a domestic reputation. When three franchises bid together, the price rises from demand, not from ability.

Here the separation of commercial value from sporting value is at its clearest — ₹7.2 crore and three runs, a case study in one line. And the market has already corrected itself. The release by Delhi, then the much cheaper acquisition by Gujarat Titans, is the market saying in its own language that the first price was an artefact of a bidding war.

This pattern is not new to the Indian auction cycle. In the same news flow, T Natarajan returning to Sunrisers Hyderabad at a reduced price, and Zeeshan Ansari joining Delhi Capitals, illustrate the same logic. First valuation overshoots; then the market settles.

There is a side effect of that correction nobody counts. A lower price also lowers the 'must play' pressure. A high price is a burden, but sometimes the burden is what forces opportunity. A cheaper acquisition means lower risk for the franchise — and less disruption for the batter, which can also mean fewer matches.

One more thing belongs here, which I have written repeatedly over recent years: for Indian wicketkeeper-batters, the domestic route is in fact the more reliable path, not the IPL route. Popular belief says the opposite — that the T20 league is what lifts young players fastest. In practice, for Pant, for Kishan, and now for Kushagra, a red-ball domestic record has been the cause of the first big call-up. The IPL gives money; the domestic circuit gives places.

An uncomfortable truth belongs alongside this. Kushagra's India A call came by way of someone else's injury. That is not his fault; it is the system's normal operation. But it means his path is not entirely in his own hands. If Pant returns fit and Kishan returns to form, the slot narrows again. The biggest obstacle in the path of young keeper-batters is not their own form, but the length of the keeper-batter queue.

So what should be watched now? The honest answer: the India A matches in New Zealand. That is his first genuine overseas test, and adapting to overseas conditions has been India's long-standing weakness. How a batter who averages 73.60 in India performs abroad is a question domestic data cannot answer.

But a trap must be avoided while watching that tour. Concluding from one century in New Zealand that he is ready would be as wrong as concluding from one duck that he is not. What needs watching is the floor, not the ceiling. The lowest score of the series, and how many balls he faced in those innings — those two numbers will say more.

I travel with a notebook, a charger, and the assumption that kickoff will be late. The notebook is open here too, with two numbers written beside Kushagra's name in two columns: 132 and 3. Whether the distance between those columns narrows over the next six months is the real question. And while waiting for that answer, it is worth remembering that an IPL price and a domestic run ledger are never written in the same book. Two separate books.

The beat is not the noise; it is the interval between two balls. In Kushagra's ledger the interval is currently long — 266, then 101, then 113, then 10. The question is not whether those peaks are real. The question is how many overs until the next one.