The Ranji Load Ledger: Nobody Writes Down the 240 Overs

A number went around after the Ranji Trophy final in Nagpur last February: 69. Vidarbha's left-arm spinner Harsh Dubey took 69 wickets that season, the most by any bowler in a single Ranji Trophy campaign. The scoreboard, the record book, the trophy — all of them found room for it.

My notebook has other numbers next to it that nobody asks about. Across the middle two days of that final I stood near the square-leg boundary, in the small press block where there are forty-four chairs and nineteen people sitting. What you hear from there does not travel to the commentary box. A quick does not remember which spell of his season he is in.

One of them came on for his fourth spell and hit the deck first ball. In the next over, bowling to the same spot, his follow-through dropped from three steps to two. The scoreboard did not move. There was no speed gun at that match. I wrote down one line: the rhythm broke before the scoreline did.

I read the medical before I read the highlight reel. Highlights keep the wickets; medicals keep the over counts. And in Indian domestic cricket, the over count is a ledger nobody keeps in one place.

The calendar nobody lines up side by side

Start with the shape of last season. The Ranji Trophy carried 38 teams — 32 in the Elite division across four groups of eight, and six in the Plate group. Elite sides played seven league matches and then the knockouts. The 2026-25 tournament began on 11 October, ran through the group stage into mid-January, moved to knockouts in February, and ended with the final from 26 February to 2 March in Nagpur. Vidarbha won a third title; Kerala reached a maiden final and lost.

Three other competitions have to be fitted inside that calendar. The Duleep Trophy in September, which from 2026-25 was staged in a new four-team format. Then the Irani Cup. Then the Syed Mushtaq Ali Trophy and the Vijay Hazare Trophy. And immediately after all of it, from late March to late May, the IPL.

For a frontline Indian quick who is a regular for his state and plays in the IPL, the calendar runs September to May. Nine months. Red-ball, one-day, T20, travel, camps, trials.

If you sit down and count one quick's overs across ten Elite-group matches, the number you arrive at is recorded nowhere in Indian cricket.

So I sat down and counted. Across three seasons, scorecards alongside my own notebook. There is one caveat and one condition before I go further. First, I am not leaking anyone's medical file. These are match-by-match over counts from scorecards, plus spells I watched. Second, no domestic competition publishes spell-level data. You can get overs bowled; you cannot get how long a spell ran, how many minutes of rest sat between spells, or how many hours of travel sat between matches. So the figures I use are estimates, and I am labelling them as estimates. That is not a disclaimer. It is the complaint.

How large the over count actually is

A frontline quick in an Elite group plays seven league matches and a knockout — eight first-class matches. Bowl an average of 30 overs a match and the season lands at 240 overs. Thirty overs across four innings is not unusual; in Indian four-day cricket that is the top-order quick's job. Some bowl 55. Some bowl 18. The average sits there.

240 overs is 1,440 deliveries. On nearly every one of them a quick spends 80 to 90 percent of his physical capacity, with a maximal effort every four to six balls. Over six months, 1,440 deliveries accumulate. Add the Duleep Trophy — up to three matches, another 70 to 80 overs. Add the Irani Cup, one match, 25 to 30 overs. Then the ball turns white, then it turns T20.

Now place the IPL beside it. In one IPL season a frontline quick plays 14 to 17 matches at a maximum of four overs each. That comes to 56 to 68 overs. A full T20 league delivers a quarter to a fifth of what a domestic red-ball season delivers — and there is no public argument about the red-ball season.

The IPL's 68 overs get workload management because there is money in them. Ranji's 240 overs get nothing because there is no money in them — and there is only one body.

One qualification matters here, or the comparison becomes unfair. A T20 over is not a first-class over. In T20 almost every ball is a maximal effort; in red-ball cricket the overs are sub-maximal but far more numerous. Sports science measures these as two separate loads — intensity and volume. Both do damage, in different ways.

So the real question is this. Who tracks intensity in the Indian system? The IPL does. And who tracks volume? Nobody.

The stadium was empty, so the notebook got loud

The R.G. Stadium in Mumbai, the Chinnaswamy in Bengaluru, the Bengal Cricket Academy in Kalyani — group-stage crowds of two or three hundred, sometimes fewer. Fewer cameras means fewer broadcast microphones. Sounds that normally drown in a crowd become clear.

Which is why I imposed a condition on myself. Every sound must be tied to a material cause, or it is literature, not reporting. Empty-stadium romance is not my job.

First, the pitch of the grunt. A quick's grunt starts low in the day and lifts as he releases. By the back end of the second session it flattens. That is not mood. That is glute and core fatigue.

Second, the boot. The scuff a quick digs into the popping crease is deep at the start of a session and shallow at the end. When the delivery stride shortens, the boot stops hitting the ground and starts dragging across it.

Third, the follow-through. It can be counted — four steps, three steps, two steps. At three, the end of his spell is close. When someone says a bowler has lost his rhythm, I say no: he has not lost a ball. He has lost a step.

Fourth, the gap between overs. In the first session, 45 seconds from the end of one over to the start of the next. In the third session, 80, sometimes 95. Ball-boy delays, glove changes, cap changes — all of them tell one story. In televised matches the gap closes, because the clock is running. Where there is no clock, the body takes its own time. That time is the data.

None of these four markers is, by itself, tactics. Bowling slowly and bowling slowly because you are exhausted look identical. One is a decision; the other is a calendar. In domestic cricket, in a four-day match in November, you can tell them apart — if you have an over-sheet beside you. I had one.

I started writing down loads because nobody else was

1. I was in high school in Mumbai. I began volunteering as a data logger with the Mumbai City FC under-18 side. Forty-two training sessions, RPE, sprint counts and sleep hours for 23 players. The coach ignored my first report. So I re-watched every session tape and found that a 3-2-4-1 build-up shape had produced 17 turnovers across two matches. I rewrote the report as a one-page table and took it back.

That habit followed me into writing. A verified training-ground number before any opinion. In cricket, that number became balls bowled, spells bowled, minutes between spells.

In 2026, bubble football. The ISL in Goa. I logged matches remotely. Twenty games, 11 clean sheets, 24 goals, 62 percent average possession under Sergio Lobera. But the numbers taught me less than something else did. The stadiums were empty and the camera count was low, so bench talk, ball-boy delays and the sound of boots on wet turf all carried. That is where I learned to write silence as evidence. It is also where I learned that for a sound to be evidence, it has to attach to a material cause.

Who actually absorbs the cost

Now to the real question.

A quick who bowls at 135 to 140 kph at 17 or 19 is pulled into the main current fast. Four-day matches for his state, the Duleep Trophy, an India A series, IPL net sessions, a franchise pre-season camp. Physical age and cricketing age are two different measurements, and nobody reconciles them.

At 20, bone, core muscle and conditioning base are still being built. Yet he is called at a rhythm designed for a 28-year-old with a decade of load behind him. And nobody keeps the proof, because keeping it is nobody's single responsibility — not the state association's, not the franchise's, not the board's.

On the two-source rule: I spoke to two support staff members, from different teams, and both said the same thing. They count a bowler's overs; that is part of the job. But at the end of a season the count is filed nowhere. A notebook, a pen drive, a spreadsheet. Then the season ends and it stops.

So which is more dangerous — 22 overs in a match followed by eight days off, or 28 overs followed by a three-day turnaround and fourteen hours on a bus? Nobody has that answer, because nobody has asked it.

What a register would look like

The solution to a problem this large is embarrassingly simple, which is exactly why it is uncomfortable.

Column one: balls bowled, spells bowled. Column two: average spell length and minutes of rest between spells. Column three: post-match RPE. Column four: sleep. Column five: days between matches and travel hours inside that gap. Column six: short spells — anything under six balls.

Fill those six columns across one season and Indian cricket reads the story of its own domestic pipeline for the first time. Right now that story is read out of injury reports, where the answer is always the same: bad luck.

And here is the so-what. A ledger changes the question. Not “why did his hamstring go,” but “why was he sent out that week in the first place.” Where a cause is written down, a decision can be changed. Where only a date is written down, only blame remains.

What everyone says, and what is true

Now the unpopular part, because the easy version has already been said by everyone else.

The easy version goes: the IPL is burning bowlers out. The reality is close to inverted. In Indian cricket the IPL is now the most regulated environment there is. Fixed windows for injury replacements, in-house strength and conditioning staff, rest built into the match schedule, insurance, and load data shared with the board. A quick will bowl more than four times as many overs in a continuous red-ball season of Ranji, Duleep and Irani cricket as he will in an entire IPL — and that red-ball season has none of those four safeguards.

The IPL is not the problem. The problem is those eight months when nobody is watching.

That is the first misreading from outside. The easy deadline story is league versus country. The training-ground story is far less attractive, because it has no villain — only an empty column that nobody fills. No villain means no television debate, and no debate means no decision.

The second misreading is more popular still. Plenty of people say domestic cricket means less pressure, so overs there do not need counting. But the four-day over is the most deceptive load of all, because it never shows up in intensity; it accumulates in volume. The assumption that ten deliveries at 128 kph are safer than one at 150 kph is widespread. Elbows and hamstrings do not accept it.

Here I follow my own rule. I do not declare a trend from ten matches or one season. I did not call Morocco's 5-4-1 a new meta after one World Cup, and I am not doing it here. I am not arguing the domestic calendar must be broken up. I am arguing the count must be kept. Numbers before decisions; columns before numbers.

Where the next signal sits

Three things I will watch next season.

First, the calendar: whether a mandatory gap appears between domestic first-class matches, and whether it is calculated around travel hours rather than just match dates. Second, the paperwork: whether NCA monitoring extends past central contracts to cover domestic-first quicks. Third, the sound: whether a quick can still hold a four-step follow-through in the final week of the season. If he can, the count is working.

If none of the three happens, then next February, on the middle day of the final, another quick will walk into his fourth spell, his follow-through will drop from three steps to two, and the scoreboard will say nothing at all. The ground will be empty again, and the notebook will be the only loud thing in it.

The question is not who won. The question is who is writing down the 240 overs.

I am.