The 105 Lesson: Bangladesh's T20I Batting Is Actually Written in Overs 7–15

Afghanistan made 115/5. A target of 116, 120 balls in hand. On the drying surface at Arnos Vale the ball kept holding up as evening humidity set in, and Bangladesh were bowled out for 105. That night my laptop had a T20 tracking sheet open, and I was logging a code for every single delivery between overs seven and fifteen, recalculating strike rate after each spin over. The reason is simple: I have been sitting in the stands in Rajshahi with a notebook since 2026, and that notebook taught me that the top line of a scorecard sometimes lies.

What the scorecard does not show is this. Chasing 116, Bangladesh scored 37 in the six-over powerplay for the loss of two wickets, which on that pitch was not a catastrophe. The damage came between overs seven and fifteen: twenty-eight dot balls in nine overs, four boundaries, twenty-nine runs. A T20 match is not decided in the powerplay. It is decided in overs seven to fifteen, where the spinners bowl and the scoreboard goes quiet.

On social media that night the argument was about the batting order at the top. Several people insisted a more aggressive powerplay would have changed the game. I was busy adding a column to my sheet that I labelled the Anchor Tax: how many runs a surviving top-order batter costs the side by consuming deliveries at a rate the chase cannot afford. The early result was not surprising. It was uncomfortable.

Context: Dhaka pitches and a mistaken diagnosis

Bangladesh's T20 identity has been built over a decade on the slow, low, spin-friendly surface at Mirpur. At home, the spinners control the tempo between overs seven and fifteen, and that structure is where the team wins most. The problem is that selection philosophy and batting philosophy are running to different rhythms. When the side travels, to higher-bounce pitches and bigger grounds, the same anchor-first batting structure cuts its own legs off.

At the 2026 T20 World Cup, India posted 196/5 in the Super Eight and Bangladesh replied with 146/8 — a fifty-run defeat. In the group stage, Bangladesh made 159/5 to beat the Netherlands by 25 runs, and chased Sri Lanka's 124/9 with 125/8 to win by two wickets. On the surface those scorelines look random. In ball-by-ball tracking they tell one story: when Bangladesh kept their boundary rate in overs seven to fifteen above five per over, they won. When it fell below four, they lost.

I started a newsletter called Expected Truth in 2026, and it was about football xG. Writing about Messi's 2026-17 La Liga season — 37 goals from 26.3 xG, a +10.7 overperformance — taught me that numbers do not discover things. Numbers ask questions. Cricket has no xG, but it has a distribution of dot balls, a boundary rate, and a cost ledger for deliveries. I moved from a Rajshahi newsletter to live World Cup analysis, and the discipline never changed: every ball needs a code, or the story stays a story.

The core: the four columns I count

My Dhaka sheet has four permanent columns. I have written down the definition of each one so that anyone can later test the result, and so that I cannot cheat myself.

One, MOB% — middle-overs boundary rate: the share of deliveries between overs seven and fifteen that go for four or six. In T20 cricket that window usually features two or three spinners, a spread field and the tightest catching cover. Boundaries are most expensive there, and that is exactly where Bangladesh stall.

Two, DB% — dot-ball rate, in the same window. If a 24-ball spell yields six dots, in a low-scoring match that is not six runs — it is six runs of pressure, and pressure produces the wrong shot in the next over.

Three, SEI — spin economy index: runs per over against the opposition's spinners, normalised for pitch type. On a Mirpur surface 6.2 is healthy; on a flat Caribbean deck 8.5 can be healthy too.

Four, the Anchor Tax: deliveries consumed by a top-order batter, multiplied by how far his scoring rate falls below the team's required rate. In plain terms, a 45 off 40 looks like a near-fifty on the scorecard, but the column tells you how many runs he mortgaged to the clock.

Taken together these four columns showed me a pattern I have tracked since 2026. Bangladesh's T20 results correlate weakly with powerplay strike rate and much more strongly with middle-overs MOB% and DB%. In my own log, holding those two variables together forecast match outcomes within roughly six or seven cases out of ten; powerplay strike rate alone was far less accurate.

One thing needs stating clearly. Bangladesh's middle-overs squeeze in the 2026 World Cup was not the failure of a single batter. It was structural. The squad contains few batters who can score against spin between overs seven and fifteen, and those who can are often not at the crease, because the powerplay blueprint fills both top slots before the window opens. A batting order is architecture. If nobody leaves room for a roof, the rain is not the roof's fault.

Mehidy Hasan Miraz and Towhid Hridoy are the most discussed cases. Their strike rates inside that window sit below what the phase demands, yet they routinely walk in at the worst moments — at number three, immediately after the powerplay, on a surface that has gone soft while the spinners are still finding their length. My sheet carries two numbers beside their names: their average strike rate in that window, and the average match-phase they enter it. The second number shows the issue is rhythmic, not personal.

A striking comparison comes from Nepal. On 14 June 2026 in Kingstown, Nepal made 114/7 and South Africa reached 115/7 to win by a single run. On resources Nepal sit far behind Bangladesh, yet in that one match they managed tempo better than Bangladesh generally do. Morocco showed football that a highly organised, under-resourced structure can drag a wealthier opponent into a scrap. Nepal's night was the cricket version. The difference is that Nepal were held together by a deliberate plan, while Bangladesh have often played out matches without one.

I will declare the limits of this analysis up front, because the biggest trap in a spreadsheet is fudging your own weighting. I have deliberately left out toss, dew, wind patterns, pitch age and umpiring interventions. Adding factors to a written piece weakens every factor, and that is not analysis, it is data fitting. The Caribbean pitches of the 2026 World Cup are also not comparable to Dhaka surfaces, so I reset the MOB% threshold for every series. I publish my predictions and track them publicly, because a model that cannot be proven wrong is not a model.

The contrarian angle: powerplay strike rate is a slogan

Now the part where I argue against my own instinct. The nine hundred words above may read as if I am downgrading the powerplay, and I am making no such claim. Bangladesh's powerplay is poor — the number is real. Across several recent series our dot-ball rate in overs one to six sits above the competition average and our boundary rate below it, and that pattern holds across a four-to-five-year sample.

The problem is telling coincidence apart from cause. Weak powerplay batting and weak middle-overs batting grow from the same root: limited strike-rotation skill and poor shot selection under pressure. Treat those as separate symptoms and you treat the wrong patient. Expected goals are confessions, not predictions — and so is powerplay strike rate. Bangladesh's real damage is not in the opening deliveries. It is that silence on the scoreboard somewhere between over nine and over thirteen.

This is where two external structural forces push in.

First, the way the Impact Player rule and bench strength in franchise cricket have turned the last six overs into a grind of attrition has entered international T20 under a different name: the death specialist. The consequence is that the last five overs are being priced higher and the middle nine overs lower. But a side crawling along at 6.5 an over through the middle nine has no wickets left to launch with. The advantage of turning the final twenty minutes into a war of attrition belongs to deep squads — and in T20 that means the last five overs. For everyone else, the rule is a new kind of decline.

Second, fitness management. Resting fast bowlers in bilateral series is now called workload management. I have taken a twelve-month calendar and found that the rest almost always lands around the fixtures with the lowest promotional value — not in board revenue terms, but in audience terms. Where the sponsors are bigger, the star plays. Where they are smaller, he is 'rested'. That is not a rest policy. It is a commercial schedule in disguise. And the bill is paid by middle-overs batting, because changing a pace bowler changes bounce and release height, and Bangladesh's middle-overs plan cannot absorb that change.

One further point, because reality matters more than philosophy here. Bangladesh's strike rotation against spin between overs seven and fifteen is limited, but part of that is entirely pitch-driven. On a Mirpur surface where the ball grips, strike rotation is almost impossible, and the home formula for winning runs the other way — squeeze with spin. So where is the fault? The fault is that we run the same template on every surface. The formula that works at home travels abroad as a wrong strategy.

Takeaway: what to watch in the next window

In the coming T20 cycle I will be watching three things, all of them situation-neutral.

First, the dot-ball rate of the young leg-spinner Rishad Hossain. A wrist-spinner who turns it both ways makes strike rotation close to compulsory for the opposition, which in turn pushes our own batting tempo upward.

Second, the over number at which Tanzim Hasan Sakib and Nahid Rana finish their opening spells. If a seamer burns through the six powerplay overs, opposition batters get a free window to settle between overs seven and fifteen. I am now tracking that logistics detail series by series.

Third, the ball number at which Jaker Ali or an equivalent finisher enters between overs seven and fifteen. Bring him in at ball 26 and MOB% rises. Bring him in at ball 40 and only the Anchor Tax rises.

The spreadsheet remembers what the stadium forgets. The real lesson of that night at 105 was not on the pitch. It was in the silence of overs seven to fifteen. When someone next tells you Bangladesh's problem is the powerplay, open the scorecard and say: look at overs nine to thirteen. If the boundary count there is under five, the rest of the arithmetic can be guessed at.