The Mirpur Powerplay Baseline: The Ten Matches You Must See Before Trusting a Control Percentage

That night is still stuck in my notebook. A T20 international at Sher-e-Bangla National Cricket Stadium in Mirpur, Bangladesh 42 for 1 after six overs. The broadcast graphic was loud and clear — control percentage 78%, with the commentator calling it an excellent powerplay. I shut my ball-by-ball log from my desk in Rangpur.

Excellent against what? On Mirpur's low, slow, turning surface, a batter only has to middle the ball for the control percentage to climb — runs are optional. The same 78% on a flat Caribbean deck tells a completely different story. A number does not speak on its own; it speaks when it is placed beside a declared baseline.

Since that night I have not let go of one question: what is the true baseline for Bangladesh's powerplay control percentage, and how many matches must be seen before it can be called a trend?

Baseline first, opinion second

I have watched cricket for 38 years. In 2026 I did radio commentary on the Bangladesh–Kenya match at the ICC Trophy — the match that opened Bangladesh's door to the 2026 World Cup. The lesson came early: when emotion arrives first, numbers get pushed back, and when numbers get pushed back, decisions go wrong.

In 2026, at 45, I began writing weekly data threads on the English Premier League from Rangpur. The Burnley thread first looked like noise until I sorted it by PPDA — only then did it become clear that Sean Dyche's low block was efficient, not passive. A new media outlet in Dhaka republished it. That is where my rule was born: no tactical claim without ten matches of PPDA and xG.

Football metrics, however, do not transplant cleanly into cricket. PPDA measures pressing intensity in football. Its nearest cricket relatives are powerplay control percentage, dot-ball rate, boundary rate, and wickets in hand at ten overs. These four indicators change meaning when the venue and conditions change.

Method note: every number here comes from my cleaned ball-by-ball log. The powerplay is overs 1–6, the middle phase 7–15, the death phase 16–20. Pitch type, daylight or floodlights, and match state are tagged separately. Where the sample is small, it is stated. Without a published method, a number is an opinion, not evidence.

Control percentage and run rate do not rise together

One thing kept returning in my ten-match rolling splits, and it is the central finding of this piece:

Control percentage and run rate are inversely related. Where control rises, run rate falls — because control rises precisely when a batter declines to take risk.

Place the Mirpur baseline beside the Sylhet baseline and it becomes obvious.

| Environment | Powerplay control | Powerplay run rate | Dot-ball rate | Boundary rate | Sample | |---|---|---|---|---|---| | Mirpur (slow, turning) | 78% | 6.9 | 43% | 10% | 18 matches | | Chattogram (mixed) | 74% | 7.6 | 38% | 13% | 12 matches | | Sylhet (flat) | 71% | 8.4 | 35% | 15% | 11 matches | | Overseas, flat deck | 67% | 8.1 | 36% | 14% | 14 matches |

At Mirpur control is highest and run rate lowest. At Sylhet control is lowest and run rate highest. Read only the control percentage and you will conclude Bangladesh's powerplay batting is at its best in Mirpur. Read the run rate too and you will understand batting is in fact hardest there.

This is the weakness of the broadcast graphic. Control percentage is a neutral measure — it records whether bat met ball. But at Mirpur, bat meeting ball is easy while hitting boundaries is hard. The slowness of the pitch quietly enters the batter's statistics disguised as skill.

A ten-match threshold without conditions misleads

My rule is ten matches. But combining Mirpur's 18 matches with Sylhet's 11 makes the ten-match threshold meaningless, because data from two different conditions are being mixed.

So I now pre-register the threshold in writing: how many matches, and inside which condition band. Ten matches for Mirpur, ten for Sylhet, a separate ten for overseas flat decks. Split that way, the picture reads:

— At Mirpur, powerplay control has held a stable 76–80% band across ten matches, while run rate stays locked between 6.7 and 7.1. — At Sylhet, control fluctuates in a 69–73% band, with run rate between 8.1 and 8.7. — Overseas on flat decks, control is the most volatile — anywhere from 63% to 71%.

The third line matters. Control is unstable on flat decks because batters take risk there. Taking risk increases mis-hits, control drops, but the score rises. So falling control does not mean falling skill — often it is evidence of aggression.

New ball and wrist-spin: how the pitch builds the number

At Mirpur, Taskin Ahmed and Mustafizur Rahman's new-ball spells, followed by the wrist-spin of Mehidy Hasan Miraz and Rishad Hossain, tie down opposition batters. Notice, though, that Bangladesh's own powerplay control rises for exactly the same reasons: the ball arrives slower, the bounce is lower, half-volleys are scarce.

The pitch that helps Bangladesh's spinners is the same pitch that beautifies Bangladesh's batting control statistics. One cause, two different directions.

Here the split appears. The opposition batter is playing on the same surface, yet the graphic shows only Bangladesh's batting control, never the opposition's dot-ball rate. If Mirpur's 43% dot-ball rate is true for both teams, then Bangladesh's 78% control is not proof of unusual batting talent — it is the ordinary consequence of the surface.

And this argument is not confined to home. At the 2026 ICC Men's T20 World Cup, Bangladesh reached the Super 8 — but there was no Mirpur pitch there. The United States and Caribbean decks were comparatively flat, and in that environment powerplay control dropped to around 67%. Same team, same batters, a different number — and the difference was made by conditions, not talent.

Judging an innings takes two z-scores

If an opener's powerplay control at Mirpur is 84%, it looks superb. But if the baseline is 78%, his true contribution is six percentage points — close to negligible, and lost within the noise of a single match.

I therefore ask for two numbers together: the deviation from baseline, and the z-score of that deviation. Mirpur's average powerplay control is 78%, the standard deviation roughly four percentage points. If someone bats through the powerplay and makes 80 off 50, his control may be 70% — but his run rate is 9.6, more than six times the baseline deviation, a z-score near +2.5.

In other words, judging an innings requires placing the z-scores of control and run rate side by side. Read only the safe indicator and every risk-taking innings disappears — and that is the biggest blind spot in identifying batting talent. Someone who is not an outlier against the baseline cannot be called superb; and someone who genuinely is an outlier should not be buried under the excuse of a baseline.

The contrarian angle: correlation is not causation

This is where the largest trap sits. Bangladesh's home record is strong and home control percentages are high — put the two facts together and it is tempting to conclude control causes victory. That is coincidence dressed as causality.

The real cause is the pitch. The surface that helps spinners simultaneously inflates batting control and suppresses scoring. Control does not produce wins; control and wins are both children of the same parent. Mistake the variable for the outcome and the analysis walks off in the wrong direction.

The second trap is importing football metrics. PPDA measures an opponent's defensive actions — behaviour without the ball. Control percentage measures execution with the ball. Their causal directions are opposite. Using control percentage like football's xG collapses cricket's phase structure.

The third trap is turning the ten-match threshold into ritual. Without pre-registered conditions, ten matches is only delay, not rigour. Adding Sylhet's eleven matches to Mirpur's twelve does not make a number cleaner, only larger.

The fourth trap is era equivalence in precedent tables. Mirpur in 2026 and Mirpur in 2026 are not the same place — boundaries shrank, balls changed, fielding restrictions changed. Build a precedent table without era adjustment and you get examples, not evidence.

The last caution points at me. Baseline-first rigour can flatten genuinely exceptional innings. So I always place an outlier's z-score beside the baseline, and I write down in advance what would prove this conclusion wrong.

Takeaway

Over the next three matches I will watch two signals. First, whether the middle-over spin control band at Mirpur holds between 76% and 80%, or whether an opposition attack breaks it. Second, whether an opener's control falls while his run rate rises on an away flat deck — if it does, that is not a bad sign, it is the right sign.

The real question is still not printed on the graphic: does the pitch that builds the number ever appear on the scoreboard?