The Over After Drinks: Bangladesh's Missing Middle-Over Runs and the Khulna Hand-Ledger

It was 2:20 a.m. in Khulna, and I kept rewinding the stream to a single over — the 26th, the first over after the drinks break. The scoreboard said 124 for 3. My hand-coded ledger next to that over carried two figures: four dot balls, one strike rotation.

One strike rotation means the batsmen crossed ends once in six deliveries. Four were empty. The over cost four runs. Bangladesh lost the match by nine, and across the 24 overs after that one they added 114 — a rate of 4.75.

I had written the numbers down; on that night they did not speak. What spoke was the shape of the over: six balls, four blanks, one walk. The game was running, but the over had stopped. That gap is today's question.

I began with a hand-coded ledger, and the numbers learned to confess.

Context: Why Over 26 Is A Line

In 2026, at sixty, I left a thirty-one-year sub-editor's desk at a Khulna daily and sat down to do one thing only: chart the Bangladesh Premier League by hand. Twelve teams, sixty-six matches, 4,180 deliveries. A spiral notebook and a laptop with a cracked screen were my entire studio. At 2 a.m. I re-opened the stream and coded the dot balls, the strike rotations, the direction of boundaries and the length of each delivery.

That year one sentence of mine changed. I stopped writing 'deserved to lose' and started writing 'won the shot battle 2.1 to 0.7'. Every claim now carries a figure I can open in public. Every note carries a date, so a reader can verify a trend instead of trusting a mood.

Cricket has no 60th-minute line the way football does, but it has an equivalent: the over line. In ODIs I mark four. Over 11, when the fielding powerplay ends. Over 26, the over after drinks. Over 35, the over before the batting powerplay. Over 46, where the death begins. In T20 cricket the lines move: over 7, over 13, over 16.

The 60th-minute line is not a stat; it is where matches change their minds. In cricket, matches change their minds in the over after drinks, at over 26. Three things collide there: the outfielders are now set beyond the ring, the spinners are bowling their heaviest share as the ball grips, and the dew has not yet arrived to tilt the second innings. Under that three-way pressure a batsman must choose — buy runs with risk, or bank the wicket and wait for the last ten overs.

In Bangladesh's innings I have seen the second path chosen more often. The trouble is that banked runs are never returned; only the interest grows.

My ledger holds 64 Bangladesh ODI innings from 2026 to 2026 with complete ball-by-ball coding. One clarification: these are not an official broadcaster's numbers, they are my own. Anyone can open a delivery and check. I verify results against International Cricket Council records and newsroom scorecards, but the window itself is my arithmetic.

Core: What The Ledger Confessed

I cut those 64 innings into five windows. I do not cut them by ball count but by bowling restrictions and breaks, because a match changes its mind not at the wicket but at the rule and the interval.

Overs 1 to 10: run rate 5.9, dot balls 42 percent. Overs 11 to 25: run rate 4.6, dot balls 51 percent. Overs 26 to 30: run rate 3.9, dot balls 58 percent. Overs 31 to 40: run rate 5.8, dot balls 44 percent. Overs 41 to 50: run rate 7.6, dot balls 31 percent.

Look at the sequence. Bangladesh move fine in the powerplay. Then the pace drops between 11 and 25. In the five overs after drinks it bottoms at 3.9. Then it climbs back to 5.8 between 31 and 40, and to 7.6 in the last ten. The innings is shaped like a letter: up, down, up. A batting order that changes gear three times needs a separate skill for each transition, and that is where Bangladesh's cost is hidden.

To sharpen this I built a figure I call the Intent Index — average runs per scoring shot. In the 11-to-25 window Bangladesh's index is 1.08, India's 1.21, Pakistan's 1.16, Afghanistan's 1.14, Sri Lanka's 1.11. Bangladesh do not play fewer scoring shots in this window than their neighbours; the difference is the weight of those shots. Runs come, but the manner of run-making does not change. We walk ones; we do not convert them into twos.

Widening the window exposes the picture further. In overs 11 to 30, India run at 5.6, Pakistan 5.1, Afghanistan 5.3, Sri Lanka 5.0 — Bangladesh 4.4. Curiously, Bangladesh do climb above 7 in the last ten. The team is not slow; the team is hesitant. Slowness is a decision. Hesitation is another thing entirely.

At player level the difference sharpens. Shakib Al Hasan's strike rotation is 3.9 per over, the highest in the side, and that number explains why he remains Bangladesh's most valuable middle-overs asset. Mushfiqur Rahim hits boundaries off roughly 8.2 percent of deliveries in the 11-to-25 window but owns the lowest dot-ball rate in the side; he drags runs against the current. Mahmudullah Riyad runs at a 138 strike rate between overs 41 and 50 — not an engine, but nitrous.

Among the newer group, Litton Das reads as split: a strike rate of 92 in the powerplay that falls to 71 between 11 and 25. That is not a limit of ability but a crisis of role. Towhid Hridoy leaves 49 percent of deliveries empty in the 11-to-25 window, which is not unnatural for a 23-year-old, except that on this list he is the fourth batsman — meaning two or three wickets have already gone before him. Using Mehidy Hasan Miraz as a floater pulls Bangladesh's dot-ball rate from 58 to 52 in the 26-to-35 window; a small figure, but five or six percentage points is 11 to 14 runs in an innings.

Soumya Sarkar is not irrelevant here. In 2026 I interviewed him for a piece that became my first verifiable byline, later picked up by Prothom Alo, and neither of us knew that eight years on his transition from powerplay to middle overs would become the most restless column in my ledger.

One note on silence. In the matches played in empty stadiums in 2026 and 2026, I found that Bangladesh's run rate in the 26-to-30 window fell to 3.6, below the 3.9 average of the 64 full-house matches. The reason is plain. When a batsman returns from the drinks break, crowd noise is what reminds him exactly where the scoreboard stands. Silence has a grammar, and empty stadiums taught me to parse it.

Contrarian: Symptom, Not Cause

Now I will stand against my own numbers, because duty says so. Middle-over slowness is often a symptom, not a cause. Read the 3.9 run rate of the 26-to-30 window and many will write 'slow middle order'. If I cut the same 64 innings by the timing of wickets, the picture inverts.

In innings where the opening stand lasted 15 overs, the 26-to-30 run rate is 4.9. Where two wickets fell inside 20 overs, it is 3.4. That gap is 1.5 runs an over, roughly 30 runs an innings. Half of what is called a middle-order failure is actually top-order instability. The man walking in at four is not slow; he is made slow, because by then the team's brief has changed — from winning to surviving.

The second point is what the opposition is doing. Against Bangladesh, almost every side bowls its best spinner between overs 20 and 35 and drops a sweeper to long-on, removing the cutter's reward. Through the 2026 home season this became close to a rule. That is not Bangladesh's weakness, it is the opponent's arithmetic: nobody fears Bangladesh's powerplay, they fear the weight of the last ten overs, so they slow the middle and try to ruin the finish.

Third, the pitch. On the two-paced Mirpur surface, the 26-to-30 window is the hardest passage of the day. The ball is old but there is no dew; the air is dry, the seam does not move, the skid does not quicken. In Sylhet or Chattogram, Bangladesh's run rate in the same window is roughly eight to ten percent higher. Anyone proposing to change the team must first hand over the venue list, or both the number and the alternative will be wrong.

Fourth, something I rarely write about. In innings where an opposing fast bowler was carrying an injury or withdrew before the match, Bangladesh's run rate in the 26-to-30 window rises to 5.2. Medical detail is never fully disclosed, sources usually leak, and the truth stays in the batsman's ledger — whether a stretch branded as poor form was in fact a knee carry, data will never say, only the team. I can only write this: where injury information is genuinely transparent, the rate of analytical error falls dramatically.

One trap cannot be skipped. Bangladesh run at 7.6 in the last ten overs, and I myself once wrote that 'the last ten overs are Bangladesh's real strength.' I had not placed that run rate beside the boundary count. Side by side, a large share of those boundaries came when the innings was already lost. The team is not a spreadsheet, but a spreadsheet can learn to listen — provided the question is framed correctly.

Takeaway: The Next-Round Signal

So what remains for me is one window prediction, with its metric. The answer to Bangladesh's middle-overs question, I think, is not overs 26 to 30 but overs 27 to 35. Those nine overs are where a side decides the price at which it will sell its innings. In the coming series I want one metric watched: the dot-ball rate of the No. 4 batsman inside that window. If it falls below 46 percent, the innings' foundation shifts upward, and the 7.6 run rate of the last ten overs becomes genuine strength rather than an eraser.

If anyone asks why so much complexity, the answer is simple. I am a data monk; I sweep the same columns until they become prayer.

What I missed: On 28 September 2026, in the Asia Cup final against India in Dubai, Bangladesh chased 223 and lost by three runs, with Mushfiqur Rahim making 144. My earlier note said the final was lost in the middle overs. Recounting over by over, the error was in the last five overs — Bangladesh's dot-ball rate there was 41 percent, and Mushfiqur Rahim was unbeaten at the non-striker's end. I have corrected the arithmetic, not the scorecard; the scorecard said it plainly, and nobody read it properly.