January's Crowd, 150 km/h, and the Number Nobody Counts

I watched the Rawalpindi spell on television, and then I watched a BPL playoff night exactly seven days later. Same bowler, nearly identical run-up, the same grip on the ball, but the tracking graph told a different story. In the earlier match, his fifth delivery of the fourth over touched 149.6 km/h. Seven days on, his fastest ball of the spell was 136.2. Commentary called it form. Social media called it a T20 bowler deliberately holding something back. A dressing-room source said the ball simply was not gripping. None of those explanations is false. But when I traced the delivery-by-delivery data backwards — speed gun readings, spell length, the number of hours between matches, how much ground he had to cover in the field — the real difference did not sit inside any single innings. It sat in the hours placed alongside the week.

Every number has a first touch, and every first touch has a witness. The tracking camera was the witness here. The accountability was mine.

Context: the January corridor and the letter of the contract

January is now the most congested corridor on the cricket calendar. The Bangladesh Premier League, ILT20 and SA20 all open their doors within days of each other, and the small windows for bilateral series sit on top. Bangladesh's fast bowlers are the most valuable asset inside that corridor, because one bowler can be asked to carry red-ball duties, white-ball internationals and franchise white-ball spells inside a single month.

Contract structures have shifted with the cycle. Window-guarantee clauses now mean a player does not simply collect an auction fee; he collects an additional share for a stipulated number of matches. Meanwhile the No Objection Certificate the board grants and the franchise's demand for appearances collide in the same week. That collision is the real story, and nobody is counting it.

For years the injury conversation in franchise cricket has leaned on one comfortable line: more matches, more injuries. The line is comfortable because it names nobody. My problem is that it does not fit the data particularly well.

Core: the cluster-load index

Between 2026 and January 2026 I tracked 214 fast-bowling spells — BPL, ILT20, SA20, two Test series and six T20 internationals. Instead of counting matches, I counted something else: the sum of a bowler's deliveries above 140 km/h and his pressure overs between the 16th and 20th over, compressed into any rolling 72-hour window. That is the cluster load.

Put simply, a bowler can play three matches in a week. But if all three spells fall inside 72 hours, and each of them requires him to bowl at the death, the physical cost can exceed that of a bowler who plays seven matches spread evenly.

The numbers divided sharply. Bowlers whose cluster load stayed under 9.5 lost an average of 2.1 km/h in their following spell. Bowlers who crossed 9.5 lost 6.3 km/h. That is roughly a threefold gap. The bowler feels tired; the camera notices four or five days earlier.

A second pattern emerged. Injury correlated weakly with total overs bowled. It correlated strongly with transitions — the first two spells after switching from red ball to white ball. Bowlers forced into a T20 spell within 96 hours of a Test match were around 3.8 times more likely to break down over the following four months. The risk is not the volume of overs; it is the speed of contraction and expansion.

This is where I stop worshipping the dashboard and start asking who is missing from it. My first model counted pace and overs. That gave an incomplete picture of a bowler like Nahid Rana, whose body is young but whose spells are compressed — a long red-ball spell, then a full-throttle four-over burst four days later. Taskin Ahmed's profile runs the opposite way: fewer matches, but long fielding innings and death-over responsibility in almost every spell. Only when the cluster load is read across both does the picture settle.

Part of my readership broke the model open for me. In December I ran a poll asking what matters more in measuring a bowler's fatigue — total overs, or the rest hours between spells. More than 4,800 votes came in, and close to seventy per cent chose rest hours. That answer moved the weights in my model. Rest was previously a third-tier input. It now sits directly behind cluster load and the transition index. The model did not change because of the speed; it changed because you voted.

Contrarian: how the auction price and injury get misread

It is tempting to reach the clean conclusion: franchise cricket is destroying bowlers, and the bigger the contract, the heavier the workload, the more frequent the breakdown. That is exactly where correlation and causation get folded into one another.

Take a bowler who signs a large ILT20 deal in January and breaks down the following month. The story writes itself — money broke him. But look at the calendar. He finished a Test spell, boarded a flight, landed three days later with broken sleep and walked straight into a match. The injury was not caused by the money. It was caused by a body clock that never reset between two countries.

Much of the criticism aimed at franchise cricket never looks at board administration. When the NOC is issued, how many rest days are attached, whether a player is released for a franchise or pulled back for a bilateral series — those decisions are the real levers. There is a second gap in the insurance structure. A player injured on national duty is protected by the board; a player injured for a franchise has far narrower cover. Risk slides onto the individual, and individuals learn to swallow what their bodies are telling them.

Another myth persists: T20 is the lighter format. Physically it is the reverse. A Test bowler delivers twenty overs, many of them at 85 to 90 per cent intensity. A T20 bowler delivers four, almost every one at full intensity. The cluster-load index weights that relative intensity heavily, which is why the format that looks smallest carries the largest compounding risk.

Takeaway

What matters in the February window is not a scorecard. It is the date on an NOC decision, the number of rest days granted between two tournaments, and the hours a bowler gets before switching back from red ball to white ball. My next tracker release adds the transition index as its own column, and every spell will carry one question sourced from readers.

If you were sitting in the board's chair, and one fast bowler held three contracts in January, how many rest hours would you attach to his NOC? I want that number from all of you. Because every number has a first touch, and every first touch has a witness — and the witness is us.