Empty Stadium, Heavy Notebook: The Invisible Cost of Asia's Pacer Calendar

The stadium was empty, so the notebook got loud. On an evening last November, a right-arm quick stood at the top of his mark in a set of nets with nobody in the stands — only the sound of spikes on wet turf and one short, dry breath before release. The speed gun told me nothing. The handwritten sheet told me everything: overs bowled in matches over the previous 14 days, overs bowled in the nets, cities visited, hours spent in the air. Add the four columns and the number was 61.

The bowler was 22. Four cities, three formats, 61 overs in a fortnight. Twenty-seven of those overs came in the nets. Those 27 overs exist in no official database and no workload report. I started writing down loads because nobody else was.

When Asian cricket talks about its calendar, it counts matches. At the 2026 ODI World Cup, 10 teams played 45 matches in 46 days; India alone played 11. The 2026 Asia Cup ran on a hybrid model, with matches split between Pakistan and Sri Lanka, which meant teams travelled between two countries mid-tournament. In September 2026 the Asia Cup was staged in the United Arab Emirates, where India beat Pakistan in the final by five wickets. Sandwiched around all of it sits the IPL: 74 matches in under two months. Buried underneath is the domestic red-ball season — Vidarbha won the 2026-25 Ranji Trophy final against Kerala.

On paper the calendar looks clean. On the ground it is not. The three days after a series ends are logged as 'rest'; in reality one goes to a flight, one to a hotel change, one to the nets, because the coach does not want the bowler losing rhythm. That column is the least popular page in my notebook.

Asia's geography makes the arithmetic worse. There is no convenient direct link from Colombo to Karachi; you route through Dubai. So a three-day break before the next match is not three days. It is one training day and two days of luggage.

Which is why my first observation is not about match counts. Asia's bowling-load problem is not the number of matches; it is the shape of the gaps. Across nine years of watching training sessions closely, the biggest jump in risk came when the recovery window fell to three days and the format changed at the same time — long Test spells straight into a four-over T20 allocation. A long spell builds a thick load. A T20 spell is maximum intensity per ball. Two different fatigues accumulate in the same tissue, and both are counted in the same recovery column.

Net overs deserve their own paragraph. Match overs are countable and public. The risk is often built in the overs nobody counts. In my 2026 notebook at Mumbai City FC U-18, I logged RPE, sprint counts and sleep hours for 23 players across 42 sessions. The coach sent my first report back because it contained match overs but no net overs. Adding that column changed the picture.

Mohammed Shami's 2026 World Cup is the case worth revisiting. He missed the first four matches, then took 24 wickets in seven games to finish as the tournament's leading wicket-taker. Many read it as proof that rest works. I read it differently. What worked for Shami was not a number but a block — a defined, extended break. Twenty-four wickets in seven matches is more than three per game, but those seven games were never consecutive; each was separated by four or five days of breathing room. The start of his break was not in his control; the length of it was clearly stated.

The other direction matters too. Jasprit Bumrah's back stress fracture ruled him out of the 2026 Asia Cup and the 2026 T20 World Cup, and the return took months, not matches. A miscalculated load is never repaid in fixtures; it is repaid in months. I read the medical before I read the highlight reel, because the medical tells you what an event actually cost.

There is a layer in Asian cricket that gets discussed least: age. The heaviest domestic red-ball overs go to pacers aged 21 to 23. They are the cheapest, the most available, and the least valued in a board's ledger. A compressed Ranji schedule squeezes eight or nine matches into a few weeks, travel included — Rajkot to Pune, Pune to Nagpur, inside a single week. The bowler whose body is not finished is the one carrying the most, because his replacements are few and his objections are not heard.

The easiest accusation is that franchise leagues are the root of all of it. My notebook does not agree. League calendars are published at the start of the year, over limits are fixed, six-week windows are known in advance. The unpredictable part is bilateral series, slotted into whatever window is left over and rarely reconciled between two boards running two different sums. Leagues are published; series are guesswork — and yet the finger always points at the leagues.

There is a second misreading from outside. We assume a slow, drawish Test in Asian conditions is easy on the bowlers. Sitting in an empty ground shows the opposite. In heat, humidity and on spin-friendly pitches, a pacer's spells do get shorter, but the number of spells goes up: four spells of four overs instead of two spells of eight. Every stop-start means reheating the body. In athletics we count this for 400m runners as a reheat cost. Cricket does not count it at all. The system was sound here — until the calendar asked it a question.

The rhythm broke before the scoreline did. I have written that line in notebooks many times, and last season gave it a new meaning. In one Asian Test, a pacer's average spell length in the second innings fell from five overs to three. The scoreline was still level, the match still alive. Nobody asked me about workload that day. Three weeks later he was off the field.

So now I watch the shape of the calendar, not the fixture list. The next signals are two: how far the domestic red-ball window stretches, and whether the next Asia Cup is hosted in one place. If the tournament is split across two countries again, the travel column grows again — and nobody is counting that column today. When the boards publish the fixtures, one question is worth asking: where is the spell count? Anyone who can answer that knows what this game actually costs.