The Overs 7–15 Ledger: Where Bangladesh's Tournament Problem Actually Lives

The Night of 31 Dot Balls

On 10 June 2026, at Nassau County International Cricket Stadium in New York, the pitch was slow, the ball was stopping in the surface, and batters could not find timing on the pull. South Africa were bowled out for 113. Bangladesh's target: 114. In T20 cricket, such a small target looks like a gift and behaves like a trap — because with a small target there is no obligation to take big shots, and that is precisely where the arithmetic slips.

That night I kept a ball-by-ball ledger, one ball per cell. After the match I summed the columns: between overs 7 and 15, Bangladesh faced 54 balls, scored 38 runs, hit three boundaries, and played 31 dot balls. In the last two overs they needed 23. The innings ended at 109/7, a four-run defeat. In scorecard language this was a "close match." In the language of my ledger, the defeat had been written six overs earlier, in silence.

The quickest explanation is always the cheapest: "nobody could hit at the death." I have watched matches for years, and that explanation returns every time. Every time it points a finger at the final two overs, when the match was already lost before them. This piece is an attempt to redirect that finger.

How I Built This Ledger

For the 2026 ICC Men's T20 World Cup, I hand-charted every ball of Bangladesh's seven matches. In 2026 in Chattogram, I used the same discipline to build the first xG ledger for local football — and when press-box veterans said women do not understand tactics, I answered with raw shot maps. I carried that discipline into cricket. I split every innings into three phases: powerplay (1–6), middle overs (7–15), death overs (16–20). In each phase I calculated four measures — dot-ball percentage, boundary-ball percentage, strike rotation per ball (singles and twos), and run rate.

Seven matches is a small sample. So I added a control window: the twelve bilateral T20Is Bangladesh played in the twelve months before the World Cup. Without comparing the two windows, I would not accept my own claim that "Bangladesh bat slowly in tournaments."

I state the rules plainly, because I keep clean columns so the messy truth has somewhere to land. A dot ball means zero runs, whether the batter is out or not. A boundary means four or six. Deliberate dots (inside edges, blocks) and unintentional misses go in the same cell, because the scorecard does not separate them. My hand-charted numbers may differ from official databases by up to ±0.2; I accept that limit and proceed.

The Powerplay Is Not the Problem. Overs 7–11 Are.

The good news first. In the powerplay Bangladesh held a run rate of 7.4 across seven matches, with a boundary percentage of 15.2 — not a disappointing return. On the difficult pitches of the 2026 World Cup, that is broadly normal. Strike rotation was 0.98 per ball, meaning Bangladesh did not suffocate early. In commentary shorthand, Bangladesh's powerplay is "cautious." In my ledger, it was functional.

The real picture emerges in the next nine overs. Between overs 7 and 15, Bangladesh's run rate was 6.3 — a full 1.1 below the powerplay. Dot-ball percentage was 41, boundary percentage 8.9, strike rotation 0.71. Yet this is the phase where the field spreads, where ones and twos multiply, where spinners are less intimidating. This is exactly where Bangladesh stalled most. The death overs recovered to 8.6 — not because the intent changed, but because the tournament's clock leaves no choice.

The comparison sharpens it. Among the teams in the Super 8, Bangladesh's boundary percentage in overs 7–15 was the lowest — 8.9. India 13.4, Australia 14.2, Afghanistan 12.1. I built a simple index, the Acceleration Index: middle-over run rate minus powerplay run rate. Bangladesh −1.1, India +0.8, Afghanistan +0.4. Bangladesh's innings generally drift backwards. The late dash often only makes the score respectable; it does not bring the match back.

On that New York night the numbers were harsher still. Thirty-one dot balls in overs 7–15 means roughly 57 percent of balls in that phase produced zero runs. A strike rotation of 0.71 means just two runs per four balls between the wickets. The wickets were in hand — Bangladesh had five standing before the 16th over. In tournament chases, Bangladesh's average wickets in hand at the start of the 16th over was 5.3, the most favourable figure in the Super 8. But that stored capital never converted into death-over risk.

This is a familiar mathematical problem: wickets in hand only matter if a team opens the run-rate door itself between overs 12 and 16. Bangladesh knocked on that door in the 16th over — far too late.

Not an Intent Problem, a Sequencing Problem

Some coaches in Chattogram told me the problem was the number five position. I treated that as a hypothesis and tested it. Across the seven World Cup matches, Bangladesh's number five faced an average of 14.2 balls per innings at a strike rate of 112. That is not worse than expectation — slightly below India and Australia's number fives, but not a collapse.

The crack is higher up. Bangladesh's numbers three and four together consumed 41 percent of all balls faced, at a strike rate of 118. The two positions meant to set the innings' tempo spent balls without generating pace. By the time numbers five and six arrived, fewer balls remained and the required rate was higher — an impossible equation. The finisher's failure here is a symptom, not a cause.

The eye test says Bangladesh are afraid of big shots. The ledger says the fear is not in overs 12 to 15 but in overs 7 to 11. In those five overs, Bangladesh's boundary percentage was 7.1 — roughly one and a half times lower than in the death overs, precisely when the field is out, spinners are bowling slowly, and singles are available without risk.

Here I must be careful. Correlation is not causation. The overlap between teams that bat slowly in the middle overs and teams that lose is substantial, but it is also possible that the pressure of losing makes teams bat slowly. A team falling behind avoids risk; risk avoidance raises dot balls; dot balls deepen the deficit. Game-state noise is real here, and in a seven-match sample that loop cannot be measured apart. I am therefore not claiming slow middle overs cause defeats; I am claiming overs 7 to 15 are the room where the result is actually decided.

Venue control matters too. In the twelve-match bilateral control window, Bangladesh's middle-over boundary percentage was 11.3 and dot-ball percentage 36 — the picture is markedly better in bilateral cricket. A slow New York pitch, artificially prepared conditions, and tournament pressure together break a team's natural rhythm. There is no denying that seven matches is a small sample, and treating these numbers as final truth would be wrong. But stating the limits of a small sample is not weakness; it is honesty.

The ledger does not replace the match; it remembers what the match forgot. Folklore remembers the 109-run innings and the four-run defeat. The ledger remembers 31 dot balls, which no highlights package will ever show.

The Signals I Will Watch Next Tournament Cycle

I make no predictions. I set a decision threshold. In the next tournament cycle I will watch three numbers in Bangladesh's batting ledger, and I have fixed them before the matches begin.

First, middle-over boundary percentage must sit above 11. Below that line, death-over proficiency cannot be trusted either. Second, strike rotation must sit above 0.85 — this is the metric least dependent on pitch quality, and the bilateral figure of 0.89 proves the capability exists. Third, the run-rate gradient between overs 12 and 16 must slope upward, not downward. Who bats where matters less; which overs the innings acquires momentum in is the real question.

In the press box my colleagues usually argue about the final balls. I keep a stopwatch and look elsewhere. In the transfer market my first duty was to reconcile the story with the fee; in match analysis my first duty is the same — to reconcile the story with the columns.

The question everyone should ask is this: in your team's ledger, is the room between overs 7 and 15 sitting empty?