336 Balls, 30 Days, Zero Central Registry: A Delivery Ledger Before the 2026 T20 World Cup

February 7 to March 8, 2026 — thirty days, twenty teams, more than fifty matches, venues strung across India and Sri Lanka.

I put the ICC Men's T20 World Cup 2026 schedule into a plain spreadsheet. Then I added one column that no broadcast graphic carries: probable balls bowled.

A frontline seamer in a side that reaches the final, by my arithmetic, will bowl somewhere between 300 and 360 balls across the tournament. Back-to-back group matches, a single day between them, and travel days not counted at all. A Test seamer bowls 90 to 150 balls in an innings, but the next innings is three or four days away. Here the gap is close to zero and the intensity is far higher, because a four-over quota means four overs of attack.

The number did not shout. But intensity divided by recovery is the real variable, not matches played — and the Khulna ledger did not lie on that rule: 132 matches, 2,847 shots, one quiet conclusion. In the 2026 calendar that ratio has moved the wrong way, and nobody is keeping a central count of it.

Since SportsKhulna printed my ledger in November 2026, I have kept two notebooks. Shots in the football one, balls in the cricket one. Both ask the same question: how much load, how much rest, and who actually controls the load.

A provenance note is necessary, because a ledger is not automatically neutral. What it holds: ball-level notes from several seasons of domestic and franchise cricket, spell splits for individual bowlers, rest days between matches, and whatever injury news becomes public. What it does not hold: internal training loads, medical scans, actual travel time, and the commercial terms inside an NOC. That absence is the limit of the analysis. Skip the limit and everything else becomes a staged story.

In football every international transfer passes through FIFA TMS, and the chain stores the player's full history. Cricket has no equivalent. A board releases a bowler to a franchise league through a No Objection Certificate. The NOC normally states dates, the event, the length of the release. It does not state how many balls that bowler has already bowled this year, how many he is contracted to bowl elsewhere, or whether the central contract even carries a workload clause.

The single most useful input for an injury model never lands in any central registry.

Now the arithmetic.

A frontline T20 seamer bowls a maximum of 24 balls in a match. That creates the impression of a cap. But the cap belongs to the match, not the season. A fourteen-match tournament run is 336 balls. Add three separate competitions inside six weeks — a domestic T20 league, a foreign league, a national series. Each one enforces its own four-over ceiling, and every ball lands on the same ankle. The quota resets per competition; the load accumulates per body.

The window matters as much as the count. An international seamer's year should be judged on a rolling twelve months, not January to December, because franchise seasons are scattered. For Bangladeshi fast bowlers the rolling window is the least forgiving measure available.

Then the domestic calendar. The Bangladesh Premier League usually occupies the winter window, the Dhaka Premier League's 50-over competition lands in spring, and the National Cricket League is split across two ends of the year. A seamer who wants it can stay in competitive cricket almost continuously from October to May, with national duty and a foreign contract stacked on top. No single competition is at fault; the calendar design is.

Spell splits tell a different story again. Four overs are not four equal overs. A powerplay spell with a new ball, two fielders out, a batter searching for swing is one kind of strain. A death spell of yorkers, slower balls and boundary-line lengths is another entirely. I have watched enough matches from the gallery to notice the same thing repeatedly: at the 17th over the seamer's stride shortens, the run-up trims. A seamer's most expensive deliveries are in the last three overs, exactly when the legs are emptiest.

The physiology is unglamorous. Pace bowling's main cost is not shoulder or hand but hamstring, ankle and lumbar stress fracture. Lumbar stress fractures cluster in fast bowlers between roughly 20 and 26, before bone density has fully adapted to the load. That same age band is the most in-demand in franchise cricket — young, quick, cheap. Market demand and structural tolerance are pointed in opposite directions.

Travel sharpens the discomfort. The real cost of a compressed schedule is days, not balls. Match, next-morning flight, evening session at a new venue, match again. Recovery time is the thing that disappears. When I coded 2,412 matches played behind closed doors in 2026, the lesson was that external variables — crowds, travel, rules — change home performance. Ball load obeys the same law: count the balls and ignore the flight, and the ledger is incomplete.

The least discussed ledger is structural. Three parties currently control a bowler's load — the home board, the franchise, the player. Their objectives are not aligned. The board wants its centrally contracted bowler fit, and also wants the release fee. The franchise wants its most expensive seamer in every important match. The player wants both, because a franchise career is short and the chance does not return. No single party owns the annual ball count, so no single party carries the liability.

Bangladesh shows the structure clearly. Taskin Ahmed, Mustafizur Rahman, Shoriful Islam and Hasan Mahmud have all rotated through domestic tournaments, overseas franchises and national limited-overs duty in the same year. Mustafizur played the IPL for Chennai Super Kings in the 2026 and 2026 seasons, with ILT20 and Lanka Premier League commitments alongside. Each competition managed his workload separately. None looked at the annual ball count, because the mechanism to look does not exist.

India offers the comparison. The BCCI's central contracts contain workload management provisions, and Jasprit Bumrah's back trouble has been documented so heavily since 2026 that the board has been forced to rest him from entire series. The board does not control his IPL overs. Even the most protected and most expensive bowler in the game keeps two separate ledgers, and nobody opens both at once.

So the suspicion before the conclusion is a classical one.

Franchise cricket looks like the obvious culprit. The data does not say so, and the reason it does not is the more useful finding.

We count injuries. We do not count balls. A seamer who bowls 400 balls in a franchise season and stays fit is not a story, because staying fit is not an event. A hamstring tear is a headline within the hour. That produces what statisticians call a missing denominator. Without an injury rate per thousand bowler-days, the claim that franchise cricket drives injuries can survive for a decade without ever being reconciled. Correlation is not causation — the first lesson of ledger writing.

Rotation policy is the second problem. When a coach rests a bowler after two straight defeats, that is not load management; it is result-driven self-protection. Win and the same bowler plays on the same load; lose and he rests. The policy has no pre-registered threshold, so it does not reduce injury, it only relocates blame. Football's three-at-the-back revival carried the same logic — not progress, but a way of avoiding the reputational risk of a four-man line. In cricket, the phrase workload management often performs the same protective function.

The error log stays open: where the franchise load model failed to reconcile, I will publish it separately, because a model without an audit is only an opinion.

The 2027 ODI World Cup in South Africa, Zimbabwe and Namibia will run with fourteen teams, so the calendar is not thinning. The 2026 Champions Trophy, staged across Pakistan and Dubai, already showed that event design now answers to broadcast design.

Two signals matter, both administrative. A minimum rest-day floor that does not bend to weather or television. And a mandatory annual ball count recorded on every NOC — the transfer chain football already has. When the first ball is bowled on February 7, 2026, that registry will still not exist. The question is not only where the ball lands, but which ball it is, and who is allowed to see the count.