38 Percent on Four Shoulders: Bangladesh's Workload Ledger and the Powerplay Reckoning

I was pouring eighteen months of scorecards into a spreadsheet, sitting at home in Rangpur. The exercise is not new to me. I audited every shot of the 2026 Russia World Cup the same way, and in 2026 I placed 306 pre-COVID Bundesliga matches alongside 92 played behind closed doors to test home advantage. This time the subject was Bangladesh's pace bowling, and the window ran from January 2026 to June 2026.

One number kept returning as the ledger closed: 38.2. Across all formats in those eighteen months, 38.2 percent of every delivery Bangladesh bowled went to four men — Taskin Ahmed, Mustafizur Rahman, Nahid Rana and Shoriful Islam. The remaining 61.8 percent was shared by eleven other seamers.

Concentration on its own does not signal danger. Every team carries it. The real gap sits in the ledger's second column: of the four who bowled more than a third of the balls, at least two spent long stretches outside the announced ODI squad — because the calendar said Test, then T20I, then ODI again. The format changed; the workload did not. That distance between announcement and reality is what later gets buried in the language of injury updates.

Context: where the calendar and the squad refuse to move together

Bangladesh produces seamers through three routes: club cricket built around the Dhaka leagues and the BCL, age-group teams, and employer-backed sides. None of the three is designed to measure workload. Club owners want wins, the board wants series, players want contracts. The arithmetic nobody keeps is the one that later shows up in a hamstring or a shoulder.

The 2026-25 international calendar was especially awkward. In August 2026 Bangladesh won a Test series in Pakistan for the first time, taking it 2-0, with the Rawalpindi victory followed by a return home and a long stretch of red-ball cricket. Then came the 2026 Champions Trophy, where Bangladesh exited at the group stage without winning a match. How many rest days the seamers had across that sequence is not tracked centrally by anyone.

There is extra pressure on young quicks inside the domestic structure. Franchises now pull fast teenagers in early, because they are cheap and sellable. A twenty-year-old can end up carrying club cricket, the BCL and a franchise league in the same season. His body was not built for three different kinds of load.

I listened to the 2026 press conferences and counted the pauses, not only the quotes. I do not endorse a new tactical meta before seven matches are done — my read on Italy's Euro 2026 press was published after seven. This eighteen-month workload ledger is therefore not a story about one match.

One context adjustment matters here. Dhaka's surfaces are slow early in the season and batting-friendly later; Chattogram's behave differently in humidity. The same length from the same bowler produces different outcomes at the two venues. Without that adjustment, any cross-format comparison is worthless.

The analysis: powerplay, death overs and repeat spells

The first thing that surfaced was the powerplay. Bangladesh's run rate in the first six overs of T20Is rose in the 2026-25 cycle compared with 2026, and so did the wicket-loss rate in the same phase. The team is attacking more, and falling more. Whether that is a deliberate shift in batting profile or the by-product of failed strike rotation needs separate testing.

In ODIs the picture inverts. Bangladesh's powerplay economy is consistently better than their economy from the tenth to the fortieth over, but that comes from length and slower balls rather than pace. Against Pakistan in Rawalpindi conditions, that length worked; on the flat Dubai surface it was cut apart. Same bowler, same plan, different soil, different result.

Nahid Rana is the clean example. Raw pace put him at the centre of the conversation almost overnight, and his 2026 Test debut caught every eye. Pace carries a cost: more energy per over, longer recovery per spell. Watching those Test spells over by over from Rangpur, I noticed his fifth over was frequently slower than his first. That is not weakness, it is physics.

Mustafizur Rahman is the reverse case. Chennai Super Kings bought him for 2 crore rupees at the IPL 2026 auction, a clear valuation of a Bangladesh bowler in the Indian market. His IPL work is largely death overs plus a slice of the powerplay, the highest-pressure overs on the card. I opened the transfer ledger and found a fee was never merely a number — inside it sat how many overs, in what situations, and how much recovery time.

Shoriful Islam and Hasan Mahmud fill a gap that plain statistics miss, because much of their work comes between the seventh and fourteenth overs, where containing runs matters more than taking wickets. Bangladesh's real problem is not a shortage of seamers; it is the absence of a reliable fifth bowling option in the middle overs, which forces the first four back again and again. The concentration is a symptom, not the cause.

Sitting in the lower tier at Mirpur, I have noticed something repeatedly: when the same seamer returns for a third time in the seventeenth over, his run-up shortens and the bouncer disappears. The scorecard does not show it. The eye does. That is the point where data and observation have to be read together.

Building this ledger required no commercial tool. The manual spreadsheet I built for the BPL in 2026 travelled with me to the Russia World Cup, and it still does the job. Scorecards, ball-by-ball archives and my own notes produce most of what a black-box tool sold to this market produces. Data cost and data judgment are two different purchases, and our market routinely mistakes the first for the second.

The BPL market is a mirror here. Fortune Barishal won the 2026 title by beating Chittagong Kings in the final. Many of the bowlers who sent down the most overs in that tournament then appeared in Bangladesh's next international series as either rested players or squad members who never took the field. Read the two ledgers separately and the picture blurs; read them together and it sharpens.

The contrarian angle: more deliveries does not mean more injuries

This is my loudest caveat. The simple relationship — bowl more, get injured — does not hold in the data. Across my eighteen-month ledger, the correlation between deliveries bowled and matches missed was weak. What correlated more strongly was three other things: rest days between spells, travel patterns, and being asked for a third spell on the same day. The real variable in injury management is the calendar, not the bowling load.

I have another objection, about models. The workload framework used in franchise leagues like the IPL is built around the Indian calendar, Indian medical staff and Indian budgets. Dropping that framework into Dhaka unchanged will not work, because our calendar differs, our pool of seamers is smaller and our recovery infrastructure is different. Change a model's inputs and you change its outputs; that is not the model failing, it is our expectation failing.

The injury-disclosure question sits in the same ledger. What a club or board publishes about injuries tends to be what suits it. "Side strain" and "workload management" are labels whose difference cannot be judged from outside. In 2026 I counted pauses rather than quotes at press conferences; the same method works on 2026 injury updates.

What to watch next round

Three numbers stay on my tracker. The first is the sum of overs each seamer bowls across two consecutive franchise matches, because that is where the real pressure hides. The next is T20I powerplay wicket-loss rate against strike rate; if both lines climb together, that is not courage, it is a plan coming apart. The last is the percentage gap between squad announcements and actual appearances.

The ledger does not stop. On deadline day I learned that paperwork is the only language the market respects. So the question is not injury. The question is who is keeping the count, and who is publishing it.