Mirpur's Empty Gallery and a 31-Day Notebook: Where the Fast Bowlers' Load Actually Piles Up

The chairs in the gallery were empty. The sound of the ball boy's feet, flags flapping beside the boundary rope, and low, clipped instructions from the two ends of the pitch — that was all. At 8:40 in the morning on 11 January, in the first hour of a session on the outer wicket at Mirpur's Sher-e-Bangla National Cricket Stadium, applause came only from the dressing-room balcony; two men, three at most. I sat and counted one thing: deliveries.

A 23-year-old left-arm quick bowled 14 overs that morning, 84 balls in all. Over the last 24 of them, the ball was taking roughly 0.3 seconds longer to travel from release to the keeper's gloves — my stopwatch reading. The batter at the crease felt it too and stepped out. The scorecard recorded only 2/38; the report recorded 'a good spell'. I started writing down loads because nobody else was.

Context: three days on paper, two in reality

Seen through a fast bowler's eyes, Bangladesh's domestic calendar tells a different story. Four-day National Cricket League matches, the 50-over grind of the Dhaka Premier League, the BPL window in between, and the national team's fixtures on top — three layers live in three separate documents, but one body carries all of them. I attended 31 sessions in the last 40 days. My notebook holds spell-by-spell data on nine fast bowlers, three of them under 23.

The gap between matches is three days on paper, two in practice. Not because of flights, but six to seven hours on a bus, hotel changes, and the cooling-down hours that get eaten by the journey. That travel cost never enters any tracking system in domestic cricket.

My notebook habit began with a different sport. In 2026, as a volunteer data logger with Mumbai City FC's U-18 side, I attended 42 training sessions and logged RPE, sprint counts and sleep hours for 23 players. The coach left my first report in a drawer. I re-watched every session tape, found that a 3-2-4-1 build-up shape produced 17 turnovers across two matches, and rebuilt the whole thing as a one-page table. That worked. During the 2026 bubble in Goa, logging 20 matches taught me that in an empty stadium silence itself can be evidence — 11 clean sheets, 24 goals, 62% average possession that season; the numbers told the story, not the crowd. The stadium was empty, so the notebook got loud.

Core: the damage sits in one specific window

Fast-bowling load is usually counted in total overs, but the cost accumulates inside a defined window. In my notebook, balls 25 to 36 of a day's spell are consistently the most expensive. Two reasons show up. The front-leg brace stops holding as firmly, the foot slides slightly on landing, and the delivery's heading height changes. Shoulder rotation shortens, the release point drifts back, and length errors multiply.

The real warning does not arrive on the scorecard; it arrives in the over after the 25th ball of a spell.

The change is audible too, but only when the cause of the sound is traced to the ground. On a January morning, once the dew dries, the top layer of the pitch hardens and the fast bowler's spikes sharpen. So 'the boot sound changed' does not mean fatigue; often it means the pitch dried. Fatigue shows elsewhere — the follow-through losing a step, the breath vanishing from the release, the bouncer losing its nerve. The rhythm broke before the scoreline did, and the scoreline only confirmed it later.

How does the ball count climb? In a domestic four-day game, a fast bowler has sent down 18 to 24 overs in a day, because spin options are thin and the pitch offers no bounce — the captain keeps returning to him. Match over, three-day gap, then four more days. A 50-over game's burden is comparatively lighter in my numbers, because average per-over intensity drops. Four overs in a franchise league is not a problem on its own. The problem is the combined ledger: 30 overs in six days of four-day cricket, four more overs six days later, two hotel changes in between.

The weakest link is not total overs but recovery time and travel miles.

There is another pattern that gets discussed less. A 19- or 20-year-old quick still physically growing is pushed into senior rhythms because he does not break down yet, and because he gives someone an excuse to keep playing him. A minor injury follows, he loses his place, and returns carrying a bigger load — because by then the system has forgotten how he was built.

This is where I stop. Forty days of notebook is not a season, and nine fast bowlers are not a sample. I am not saying the country's pace bowling is collapsing. I am asking a question, and the question applies to my own sample size too.

Contrarian: losing pace is not the end

The outside explanation is easy: the pace has dropped, so he is finished. A highlight reel makes that verdict tempting, because the basis is always one spell, one match — the smallest possible sample. A writer with 22 innings of spell data cannot make that declaration from one innings. I read the medical before I read the highlight reel, because the medical keeps time and the reel does not.

The real blind spot is not tactical but structural. Club and board rotation policy exists nowhere in writing; rest is granted in verbal conversation and is usually read as punishment or reward. The physio's sheet is prepared, but nobody signs it before the toss — the captain decides, the coach under pressure decides, the table decides. The analyst who retires a batter after one innings uses exactly the same sample size to declare a fast bowler 'back'.

Let me record what would prove me wrong: ten matches of spell data in which average speed after the 25th ball is unchanged and the injury rate stays near zero. If that arrives, I will correct my notebook first and write second.

Takeaway

Watch overs 5 to 7 of the first spell in the next match — is the length holding, or is every ball a little fuller? Watch the team sheet too: if a fourth seamer is named, the dressing room has read the same sheet I have. The question in the end is this: who writes the calendar, and whose body pays for it?