Asia's Fast-Bowling Workload: Why Travel Distance Outweighs Fixture Count

Last year I spent an entire season tracking six domestic T20 competitions across Asia with one crude ledger: not how many matches a fast bowler played, but how many overs he bowled, in what kind of spells, and how many kilometres he crossed between two of those matches. Somewhere in that ledger a pattern surfaced. The young quick I was watching at the 18th over of an innings, ball soaked in dew, had bowled almost twice as much in the previous fourteen months as a fast bowler of the same age in England or Australia. Humidity in Mirpur was above eighty percent. Three days earlier he had been fielding in another country.

The scorecard does not record any of this. The scorecard records 4-0-32-2.

Living in Russia taught me a habit that still sits on the first line of every tactical note I write: In Russia, I learned that the first tactical note is always about distance, not drama. Injuries deserve the same discipline. How many balls, how many hours of rest, at what temperature, with how many travel days in between — the narrative comes after that.

Context: what Asia's calendar actually is

January and February run the ILT20, the Bangladesh Premier League and the first leg of the Pakistan Super League almost simultaneously. March to May belongs to the Indian Premier League. July brings the Lanka Premier League. In between sit Asian Cricket Council tournaments, bilateral series and ICC qualification windows. For an Asian quick, a realistic year means six countries, five time zones and at least three distinct heat zones. An Australian quick in the same year largely works two blocks, summer and winter, with genuine rest in the gap.

The distances are not hypothetical. Dubai to Karachi is roughly 1,200 kilometres. Karachi to Colombo is 3,300. Colombo to Mirpur is 2,100. Dhaka to Mumbai is 2,000. A franchise bowler can touch all four of those cities inside a four-week league window, and the day lost on each transit is not a rest day. It is an airport day, a waiting day, a body-clock day.

Heat and humidity belong in the same ledger. On the South Asian coast, summer-evening humidity climbs past eighty percent, and once dew arrives the grip weakens, so every delivery costs more forearm and shoulder. The same six-ball over that costs a bowler little on a cool dry Dubai evening costs a great deal in Colombo or Mirpur. On the league table the two spells look identical. In the bowler's own books they are two different numbers.

Core: overs, gaps and the arithmetic of recovery

The weakest unit for measuring workload in cricket is the match. A fast bowler can send down eighty overs across twenty T20 games at four overs apiece; the same bowler can send down more than ninety overs in three Test matches. The totals look close. The risk does not. Test overs arrive in long spells with lunch breaks, full nights of sleep and eight to ten travel-free days. T20 overs arrive in fragments, every second or third day, between aeroplanes and hotel rooms.

Spell architecture decides the rest. Across Asian leagues a mould has hardened over the last few seasons: two overs in the powerplay, single-over bursts through the middle, two more at the death. It sounds sensible, because the captain is matching up. But two overs four times is the same quantum of work as four overs once, at a different cost of preparation. Each return to top intensity reloads the ankle and the shoulder, and the short rest in between often fails to do anything because it is too short to be recovery at all. Where pace resources are thin, the captain keeps the bowler alive with these broken spells. The scorecard never carries that cost.

Asia is rich in spin and poor in pace, and that imbalance is the structural fault line. A domestic circuit will throw up four or five usable spinners per squad while producing, at most, two fast bowlers who can hold first-class tempo with the new ball. So the spin department rotates and the pace department does not. The same two quicks open the bowling, work the middle overs and close the innings. Their overs treble while their role variety stays flat.

The injury timelines are simply the output of that design. In 2026 Shaheen Afridi missed the Asia Cup and the home series against England with a knee problem. In the same year Jasprit Bumrah spent months out with a back stress fracture. Mustafizur Rahman's elbow and hamstring record now reads in decades rather than seasons. These are not isolated misfortunes; they are the same usage pattern repeating itself. Matheesha Pathirana's hamstring keeps returning for the same reason — an extraordinary action under repeated short-turnaround load.

The market actively encourages the pattern. At the December 2026 IPL auction Mitchell Starc was bought for 24.75 crore rupees, the most expensive bowler in the auction's history. A franchise had therefore purchased a scarce asset at an extreme price, and declining to bowl that asset looks like indulgence to a cricket-operations head. The market rewards urgency, but the spreadsheet rewards silence. The club that rests its spearhead in match four drops two points on the table today; the club that does not loses him entirely two months later. The first loss is visible now. The second is visible in six months, by which time the coach who made the call may already be gone.

One limitation belongs on the record. My evidence is broadcast footage, public scorecards and disclosed injury statements — not a franchise's internal GPS or workload data. The sample is small: six leagues, two seasons. So this is a signal, not a policy prescription. When match counts across a group differ only slightly and injury counts differ sharply, the explanation has to be sought somewhere other than the fixture list.

Contrarian: blame the incentives, not the leagues

The easy argument is to blame franchise cricket. My numbers do not support it. Franchise match counts are fixed, written into contracts, capped at four overs a night. What is not fixed is the bilateral schedule, where three matches can fall on three consecutive days and the gap between two series can be four days. What is certainly not fixed is the incentive inside the coaching room. I have sat in that room. Decisions there are made for the next match, not the next five years, and on the question of resting a fast bowler the phrase that always wins is "we need him now".

The selection pipeline pushes the same way. In Asian domestic circuits, boys who separate themselves by raw pace at fourteen or sixteen are often not finished maturing. Shoulder, elbow and lumbar tolerance is still being built while a first-class six-over spell is loaded onto that unfinished base, because the bowler already looks ready. Looking ready and being load-tolerant are different states. The physio's table detects the gap within six months. The selection table almost never does.

And one thing gets missed entirely: where the stands are near empty, nobody is anxious about the pace of the game, only about the result. An empty stadium makes every injury sound like a structural warning. When a twenty-year-old pulls up in the 19th over of an overlooked bilateral fixture, it reads as one man's bad luck. The question that should be asked is different: why is there no second fast bowler in this squad to stand where he stood? At that point the injury stops being personal and becomes a measurement of squad depth.

Takeaway: the number to watch

For the next window I will be tracking one ratio: overs bowled per recovery day. A side that rests a quick in the middle of a series — before it has won anything, not after — is telling you it keeps a spreadsheet. A side that suddenly rotates three fast bowlers for the final match of a series is only paying tribute to the calendar.

Over the next six months, pick any Asian league and watch the fourth seamer. Count his overs, then count the hours between his appearances. The injury report will arrive afterwards.