Three Frames, Four Tenths of a Second: Who Keeps the Load Ledger of Bangladesh's Pace Bowlers?

At the 2026 World Cup I was the only woman in the press box. My job designation was radio researcher, not analyst. I kept hearing that women cannot read a bowling action. So I stopped arguing and picked up a paper ledger, logging every Mashrafe Mortaza delivery: the over, the delivery number, the length of the run-up, the angle of the front-foot landing. By his 24th over the ledger showed something small and terrifying — the landing angle had shifted four degrees. I showed it to two team physios. Both shrugged. Within months his knee cartilage tore and he was out of the side.

That day my writing language changed. I put down the press-box shorthand and began writing injury notes in plain, unhurried words — no Latin, no abbreviations. The body keeps a load ledger, and the load ledger does not lie. The problem is that the ledger is written inside the body, and nobody has been assigned to read it.

Bangladesh's pace pipeline is not short of talent. Nahid Rana touched 150 kph in Rawalpindi, Shoriful Islam creates a left-arm angle, Taskin Ahmed has come back after years, and Mustafizur Rahman's cutter still troubles batters. But there is no central load database beside that pipeline. Nobody records how many overs a pacer bowled in the last four weeks, how many deliveries in each spell, how many minutes of recovery sat between two spells.

The domestic structure makes this harder. The National Cricket League is four-day cricket, starting around December. Just before or after it comes the Bangladesh Premier League — 46 matches in roughly five weeks. On top of that sits Dhaka club cricket, where a pacer chasing selection can bowl four matches in a week. Then there is the national calendar: Pakistan, then India, South Africa, West Indies. Nobody has fixed where 'extra' ends and 'normal' begins.

Australia has done this work for years, logging domestic overs centrally and reading the data on a schedule. In Bangladesh that job still belongs to the scorecard, which records overs but not load.

From years of watching from the boundary and from the screen, I would put it this way: fast bowling is a bank ledger. There are deposits and withdrawals. Many bowlers, and many people around them, only look at the withdrawals.

Start with the first number. At front-foot contact, the force travelling through the body is four to eight times body weight. For a six-foot bowler that is more than half a tonne per delivery, absorbed by the lumbar spine, the front knee, the ankle. Twelve overs in a day means roughly 150 impacts in the same place. Nobody counts them; cartilage remembers every one.

The second number matters more. Long-term Cricket Australia monitoring shows that when a bowler's weekly load exceeds 1.5 times his rolling four-week average, injury risk jumps. Both extremes are dangerous — too much bowling and suddenly almost none. The safe zone is the middle. That conclusion came from data, not from noise.

The third thing I hunt for is in the frames. Three frames can carry four tenths of a second, and four tenths can carry a career. Frame one: the last two strides of the run-up. Frame two: the delivery stride, when the front foot lands. Frame three: the instant after release, when the torso bends back.

The middle frame talks most. A tired bowler does not consciously change his landing angle; the body changes it for him. When the lower back fatigues, the front foot lands further out and the ankle rotates outward. It sounds trivial. But the cortex can no longer pass the load straight into the spine and must rotate it instead. Four degrees of rotation means half a tonne travelling down the wrong axis on every delivery. Send half a tonne down the wrong axis two hundred times and cartilage eventually objects.

In 2026 this frame work changed my job. When Zlatan Ibrahimovic's right knee hyperextended, I pulled three broadcast frames and annotated exactly those four tenths of a second. The piece was read two million times in 72 hours. The lesson: people do not want complexity, they want to see. That makes my task hard — what nobody sees with the naked eye has to be shown frame by frame.

Now to the real accounting. A large share of a pacer's annual overs comes from cricket that was never televised — Dhaka club matches, games outside the national league, warm-ups. Count only internationals and the ledger is half-written.

In a World Cup or a Test cycle, a pacer bowls every four or five days. In Europe or Australia, rain in that gap buys extra rest. In Bangladesh, the impact returns unchanged at high noon in April and May, and the electrolyte and sleep accounts often fail to balance in the last two days. Travel belongs in the ledger too — Dhaka to Chattogram to Sylhet, each journey carving out a recovery day.

Add it all up and this is what emerges: in Bangladesh a pacer is built on the big stage and broken by the arithmetic of the small one. No single series of overs decides his fate; a quiet annual reserve does, one where monthly withdrawals outrun monthly deposits. My own experience is not proof on its own, so I keep testing it against medical timelines and current video.

Now to the part I wish I did not have to write. People assume rest cures a fast bowler. On paper that sounds reasonable; in the clinic the gap is wider. Rest is not a treatment. Rest is switching off a pacer's adaptation process entirely.

Why? Bowling thickens bone, strengthens ligament, stiffens tendon. Weeks without bowling reverse that. A pacer returning after six weeks of complete rest comes back with bone, tendon and joint all weaker than six weeks earlier. The faster the return, the bigger the risk. The work after injury is not rest — it is controlled, progressive load.

The same logic casts doubt on another habit. A board that 'protects' a young pacer by keeping him away from red-ball four-day cricket is often doing him harm. Slow, sustained load is exactly where structural tolerance is built; controlled fatigue inside a spell is how tissue learns to carry match weight. So when people ask why Bangladesh's quicks cannot last in Tests, the honest answer may be the reverse of the old complaint — keeping them out of Tests may be why they never became the best versions of themselves.

And the blame is usually misplaced. In the BPL a pacer can bowl a maximum of four overs a match, but ten matches in three weeks is 46 overs of steady withdrawal. Small instalments, paid often. Meanwhile the unrecorded load of the national league and club cricket never reaches any series accounting at all. People point at the BPL, but the real invisible deficit sits in club cricket and the National Cricket League. I hold this with reasonable confidence, yet I also accept that an outsider can never fully read local cricket's fine print; so I keep checking with local physios.

So the question returns: who keeps the ledger?

My view is simple. Bangladesh needs a central bowling-load database where every delivery from the national side, the National Cricket League, the BPL and club cricket lands in one place. Every franchise contract now travels with a no-objection certificate, yet the per-over record evaporates. A physio or coach wanting to rest a pacer tomorrow first needs to know how much load that pacer actually carried last month. What is not known cannot be managed.

I did not want this column to be right. Perhaps this season proves otherwise — the numbers look different now, the calendar too, and Bangladesh's quicks may last better than all the old fears suggest. Or perhaps the old paper ledger turns out to be correct once more. We will not know today. We will know on some hot afternoon, when a pacer walks back to bowl his final over.