The Middle-Overs Dark: A Cord-by-Cord Audit of Bangladesh’s ODI Batting

In the Mirpur press box my notebook carries a line: ‘23.4 — left-arm spinner, line outside off, good length. Batsman forward, defends. Dot.’ Ten balls later, 24.3 — same bowler, same line, nearly the same length — this time swept, four. Same batsman. Between the two deliveries there is nothing but ten balls and a silence. The tape did not lie: the change did not happen on the crease, it happened inside those ten balls, in the head. So the question is not ‘why did he bat slowly’. The question is why that decision is so rare in the block from overs 21 to 30, and so easy from 41 to 50.

This piece chases that question. No hot take, no single-match story. Across the ODIs I have watched in recent years, I have logged every powerplay sequence and every middle-overs block. I built the database one corner at a time, and the pattern finally blinked.

Context: where the audit begins

In 2026 in Rajshahi I borrowed a camcorder and filmed twelve matches of my school’s U-18 football team. I counted set-piece sequences and dropped them into spreadsheet cells, one corner at a time. That habit later migrated to cricket — from football corners to cricket powerplays, the method is identical: who, when, which zone, what outcome.

The debate around Bangladesh’s ODI batting usually sticks to two poles. One pole complains — ‘no intent’, ‘weak temperament’. The other consoles — ‘the pitch was difficult’, ‘the bowling was good’. Both are weather-talk: unmeasurable, and impossible to falsify.

I wanted to measure three things. One, which block the run rate falls in. Two, where the dot balls cluster. Three, when wickets fall and whose wicket it is. Split an ODI innings into five ten-over blocks and you see that four blocks are roughly competitive, and exactly one block — overs 21 to 30 — sinks every single time.

That block is the dark room of Bangladesh’s ODI batting. To understand why the room is dark, you first have to see where the light outside it is coming from.

The powerplay is fine; the question is not there

In my log, powerplay run rates across recent home series have floated between 5.4 and 5.8. Asia’s top four average 5.7 to 6.1. The gap is not large. The dot-ball rate in the first ten overs sits at 58 to 60 per cent, higher than India or Pakistan, close to Sri Lanka or Afghanistan.

So the problem is not at the top. The Tamim Iqbal and Litton Das pairing keeps the scoreboard moving in the powerplay. In the middle overs the batsman changes, the tempo does not — but the tempo is precisely what needed changing then.

Overs 11 to 20 are not bad either — 5.0 to 5.3. Bangladesh usually lose two wickets in this block, yet the runs do not stop. That is where an illusion forms: the scoreboard reads 102 for 2 at 20 overs and the commentary calls it ‘a good platform’. But the platform starts cracking right then, because in the next ten overs the opposition throws two spinners at it together.

Overs 21 to 30: the room that stays dark

In my log the run rate from overs 21 to 30 is 4.0 to 4.3. This single block is the least productive stretch of a Bangladesh ODI innings.

If the other four blocks average 5.3, then fixing just this one block adds 10 to 13 runs per innings — before counting the benefit of not losing wickets. In ODI cricket, 13 runs is worth a wicket.

Why this block? Three causes work together.

First, spin percentage peaks here. In my log, of all deliveries bowled between overs 21 and 30, 64 to 71 per cent are spin. Spinners are operating from both ends, the field is pushed in, and the Mirpur and Sylhet surfaces are slow. Bangladesh’s home pitches are among Asia’s most spin-friendly environments — that is no secret, and the selectors know it too.

Second, the single-taking rate is at its lowest here. By my count, Bangladesh batsmen take 2.1 singles per over between overs 21 and 30; India take 3.4, Pakistan 3.0, Sri Lanka 2.8. The problem is not fours and sixes, it is ones and twos. Against spin the ball skids in, the batsman defends, the ball goes to a fielder — and there is no rotation, because the non-striker either will not give up the strike or is slow to take it.

Third, the set batsman falls in this block. Between overs 31 and 40, Bangladesh lose a wicket roughly every 34 balls. The problem is not the loss, it is the timing. The batsman who made 20 off 25 balls between overs 21 and 30 gets out in overs 35 to 40 — exactly when the six-hitting frequency should rise. A new batsman arrives, needs time to settle, and the innings stalls twice.

What the spinners do is part of the audit

The middle overs cannot be read off the batsman’s scoresheet alone. The opposing captain usually bowls eight to nine overs of spin in this block — from both ends, because the field can stay in and dot-ball pressure buys wickets. In my log, extras conceded are lowest in this block, because the ball does not come straight onto the bat; it slides.

The field setting tells the same story: short midwicket, deep square leg, long on. The single is available — but only if the batsman plays the ball into the leg side. Bangladesh batsmen push a large share of deliveries to the off side, where cover and point cut it off. The door to the single is open; the batsman simply does not walk through it.

The field setting is the opposition’s decision; rotation is the batsman’s decision — and that is precisely where Bangladesh’s largest gap opens.

A two-speed innings

Together these produce what I call a two-speed innings. Speed one, overs 1 to 20 — adequate. Speed two, overs 41 to 50 — often excellent, with a death-overs run rate of 8.0 to 8.5, comparable with any Asian side. In between, overs 21 to 40 — a break.

Here is the uncomfortable number: Bangladesh’s last ten overs frequently score far better than their middle ten, yet the two blocks do not offer the same licence to attack. In the death overs the field is out, the batsman walks in already committed to aggression, so decisions come fast. Between overs 21 and 30 the field is in, the spinner keeps the ball low, and the batsman is thinking ‘what if I get out’.

The pretty death-overs figure is also a trap. My log shows that when Bangladesh arrive at the last ten overs with five or more wickets down, that run rate falls from 8.5 to 6.8 — because the six-hitters are not at the crease. The bright final-ten score is often the repayment of a debt taken on in the previous ten.

Speed of decision — that is the core word. The data does not say Bangladesh batsmen cannot hit sixes. The data says that between overs 21 and 30 they are late in deciding. Watch the tape: defend at 23.4, sweep at 24.3. Same ball, same line. The difference is that in the first the batsman was protecting his own strike rate; in the second he was protecting the team’s run rate.

Home and away: same picture, different light

Away from home, especially on flat decks, the run rate between overs 21 and 30 rises a little — 4.3 to 4.8 in my log. But the wicket rate rises too, because on a flat deck the spinner cannot bring the ball in, yet the bounce stays true, so edges and catches multiply. The net gain is close to zero.

So the problem is not the pitch, it is the structure. At home, spin and slowness magnify it; away, boundary frequency hides it. Strip away the filter and it is the same ten overs, the same weakness.

Where the audit touches a person

Numbers alone say nothing. One evening in Mirpur, standing in the corridor outside the dressing room, a top-order batsman told me, ‘Hit a four there and it is four, but get out and the series is over.’ True. But the calculation changes when you see that not hitting the four also ends the series — because 230 does not defend, and though Bangladesh’s spin attack is Asia’s most consistent, the pressure of defending 230 grows every match.

Travelling with a team means learning the rhythm of buses, meals, and net sessions — and one thing that rhythm teaches is that cricketers hate the word ‘temperament’. It pins blame on personality, not on structure. Yet structure decides who bats between overs 21 and 30, what his role is, and who walks in if he falls.

In Bangladesh’s ODI setup the No. 4 role has been an unclear place for years. Sometimes he is an anchor, sometimes an accelerator, sometimes ‘whatever the conditions need’. When the role is unclear, decisions slow down — and overs 21 to 30 is exactly where the speed of decision is worth the most.

How the outside reading gets it wrong

Now the contrarian part. The most common outside reading is: ‘Bangladesh stall in the middle overs because they lack intent.’ That reading is comfortable, because it suggests a change of personnel will cure it. The tape says otherwise.

Misreading one: lack of intent. In my log, Bangladesh’s boundary-attempt rate between overs 31 and 40 is close to Asia’s leading sides — 28 to 32 per cent. The attempts exist; they fail because they come at the wrong time. They eat dots from 21 to 30, then take risk from 31 to 40 — the attack arrives ten overs late, exactly when both spinners are already set.

Misreading two: ‘they need an anchor.’ An anchor only works when someone at the other end is scoring five or six an over. Bangladesh’s problem is not the absence of an anchor, it is the absence of someone to rotate with the anchor. Two anchors at the crease freeze the scoreboard between overs 21 and 30 — and that is precisely what happens at home.

Third, and least discussed: the batsman who solves the middle-overs problem quickly attracts interest from other teams, and his international and franchise calendar becomes scrambled. The success story of a smaller side too often ends with a raiding offer from a bigger one. So whoever shows mastery of one block arrives tired for the next series, and the team starts again from zero. Loading that cycle onto the batsman’s shoulders alone is unfair.

What I will watch in the next three matches

Building a database is not only looking back; it is fixing one question before the next match. My question for the next three matches is this: does the dot-ball count between overs 21 and 30 fall below 50 per cent? If it does, the run rate drifts into the fives on its own, and those 13 runs arrive over ten overs.

Alongside that I will watch two smaller signals — one, how many singles the No. 4 takes (below three an over is a problem); two, how many boundary attempts Bangladesh make before the 30th over. If the numbers do not move, what changes will not be the coach but the top line of the scorecard.

In an empty stadium, the game speaks in echoes, not roars. And the echo of the middle overs is still stuck between 23.4 and 24.3.