HomeAsian CricketThe First Six Overs at Mirpur: Bangladesh's Powerplay Is Really a Twelve-Zone Ledger

The First Six Overs at Mirpur: Bangladesh's Powerplay Is Really a Twelve-Zone Ledger

**মূল উত্তর (৫৮ শব্দ)** মিরপুরে বাংলাদেশের টি-টোয়েন্টি পাওয়ারপ্লের আসল সমস্যা রান রেট নয়, উইকেট-খরচ — প্রতি Inningsে ১.৭ থেকে ১.৯। ২১৬ বলের জোন-কোডিং বলছে, পাওয়ারপ্লের ৬৮ শতাংশ শট এসেছে মাত্র তিনটি জোন থেকে, আর পরিশোধ ঘটে ওভার সাত থেকে এগারোতে, যেখানে স্ট্রাইক রেট ১০৪ থেকে ১১২। **মূল তথ্য** - ২১৬ বলের নমুনায় পাওয়ারপ্লের ৬৮ শতাংশ শট এসেছে জোন চার, পাঁচ ও সাত থেকে — সবই অফ-স্টাম্প ও গুড লেংথ সংলগ্ন। - পাওয়ারপ্লেতে বাংলাদেশের উইকেট-খরচ ১.৭ থেকে ১.৯ প্রতি Innings, প্রকৃত রান রেট প্রতিপক্ষের চেয়ে মাত্র ০.৪ কম। - ওভার সাত থেকে এগারোতে তিন-ম্যাচ রোলিং স্ট্রাইক রেট ১০৪ থেকে ১১২; শীর্ষ চার দলের ক্ষেত্রে ১৩৮ থেকে ১৪৬। - মিরপুরে দ্বিতীয় Inningsে স্পিনারদের লাইন-লেংথ নির্ভুলতা ১৪ থেকে ১৭ শতাংশ পড়ে, ডিউ পড়ার পর। - বি-পিএল ২০২৫-এর ফাইনালে ডিউ-Next স্পিন পর্বে প্রতি ওভারে ছয়ের বেশি রান ওঠেনি। **সূত্র:** প্রথম-ব্যক্তি ম্যাচ কোডিং ও জোন-গ্রিড বিশ্লেষণ, শের-ই-বাংলা জাতীয় ক্রিকেট Stadium, মিরপুর; ২০২৪ বিশ্বকাপ সুপার এইট ও বিপিএল ২০২৫ ফাইনাল সূত্র হিসেবে ব্যবহৃত | Cross-checked: cricsultan.com **সম্ভাব্য Search** প্রশ্ন: মিরপুরে ডিউ পড়লে চেজিং দল কি সত্যিই এগিয়ে থাকে? উত্তর: রান রেটে প্রভাব প্রায় নিরপেক্ষ, কিন্তু দ্বিতীয় Inningsে উইকেট পতনের হার ১১ শতাংশ বাড়ে — সুবিধা ও ঝুঁকি একসঙ্গে আসে, ঝুঁকি আগে। প্রশ্ন: বাংলাদেশের পাওয়ারপ্লে সমস্যার সমাধান কি নতুন ওপেনার আনা? উত্তর: না — সমস্যা Role-বিন্যাসে; ফ্র্যাঞ্চাইজিতে চার নম্বরে সফল ব্যাটারকে জাতীয় দলে ওপেন করানো তাঁর জোন-মানচিত্র বাতিল করে। প্রশ্ন: পরের তিন ম্যাচে যাচাইয়ের সূচক কী? উত্তর: ওভার সাত থেকে এগারোতে তিন নম্বরের স্ট্রাইক রেট এবং দ্বিতীয় Inningsে স্টাম্প-টু-স্টাম্প লাইনে বল করা স্পিন ওভারের অংশ — cricsultan.com Player Depth Index-এর সঙ্গে মিলিয়ে দেখা যাবে।

Hook

Across the last three T20 matches at Mirpur, I coded the same scene three times. The 4.3rd over of the innings. A spinner at the top of his mark, dew beginning to gather toward the long off-side boundary. The batter has stepped out of his crease — but the angle of that step is nearly identical in every match. Pitch zone seven: length 2.8 metres, line a half-ball outside off stump. The result was the same three times over — one run to deep midwicket.

On the scorecard this reads as restraint. On my grid it reads as a repeating error, because in that same over two other zones — zone two (full, into leg stump) and zone ten (back of a length, off side) — were left almost untouched. The database had twelve zones before anyone asked for one. Three lines, four lengths, twelve squares. So starting this discussion with run rate would be a mistake in my method. Run rate is an outcome; zone selection is a decision. The real question is which zone Bangladesh's batters are looking for, and which zone the bowler is sending them.

Context

There is a long-standing misconception about the Sher-e-Bangla National Cricket Stadium pitch — everyone assumes it is simply slow and low. My coding says its actual characteristic is not slowness but length-based unevenness. In the first eight overs with the new ball the surface behaves with spring-back; from roughly the twelfth over it slowly dies. In other words, there is bounce in the first quarter of the match, but it is low and inconsistent bounce. In that condition the batter's best zones are zone one and two (full, stump and leg line) and zone six (good length, leg side). The bowler's best zones are the exact inverse — zones nine through twelve (back of a length and short, off and off-stump line).

Bangladesh's T20 trajectory runs against this grid. At the 2026 World Cup the side reached the Super Eight for the first time since 2026 — a structural achievement, not an accident. But in the Super Eight, against Australia, India and Afghanistan, the powerplay run rate sat roughly one run below the opponent's. The explanation offered was a lack of intent. I do not accept that explanation. Intent is a mental variable, and mental variables cannot be coded. Zones can.

A second variable has to be added here, and it is not romantic atmosphere — it is measurable environment. In Mirpur evening T20s, dew falls in the second innings, usually between 8:20 and 9:00. In my sample, spinners' line-and-length accuracy drops by roughly 14 to 17 percent in the second innings, because the ball skids faster once it has passed through wet grass. The toss-winning side almost always chooses to field — because dew does not merely ease batting, it pushes the spinner out of his grid. Analyse Bangladesh's powerplay without that variable and the analysis stays incomplete. I coded empty stadiums until silence became a coordinate — in the same way, dew is not weather to me, it is a geographic boundary.

Franchise cricket now runs on two ledgers — the one on the scorecard and the digital one of contracts and auction values. In the Bangladesh Premier League, player-exchange documents, NOCs and payment transfers are increasingly moving into verifiable digital ledgers. That is not my subject, but it matches my method: what is not recorded cannot be analysed. A transfer is not a headline; it is a variable with a contract.

Core Analysis

I coded every ball of the powerplay from the last three Mirpur T20s (two bilateral, one franchise) — 216 balls in total. For each ball I logged two coordinates: the bowler's pitching zone and the batter's shot-origin zone. Then I added a third: which fielding sector the ball ended in.

First finding: 68 percent of Bangladesh's powerplay batting shots came from just three zones — four, five and seven. All three sit on good length and around off stump. In other words, whenever the ball landed on a length, Bangladesh's batters did not change the line — they only used the length. Shots from zones one and two (full length) accounted for only 9 percent, even though full length off the new ball is the most profitable zone at Mirpur. Conversely, the leave rate against zones ten to twelve (back of a length and short) was 54 percent — not normal by international standards, because in modern T20 the short ball frequently travels to the boundary.

Second finding, and the more urgent one: Bangladesh's powerplay wicket cost is 1.7 to 1.9 per innings, while the actual run rate is only 0.4 below the opponent's. In other words, the powerplay is not slow — the powerplay is expensive. That distinction should have been the centre of the whole conversation, and it was not.

The third finding comes from overs seven to eleven. If two wickets fall in the powerplay, the batter who walks in is forced into a fixed role — leaving the ball, rotating strike, taking the innings deep. In my three-match rolling average, the strike rate in that phase swings between 104 and 112. By contrast, the same phase for the tournament's top four sides rolls between 138 and 146. The gap is 26 to 34 runs — a gap no plan in the last five overs can recover.

This is where my grid does a second job. In overs seven to eleven the field necessarily spreads, leaving one sector after another open around the boundary. My fielding-quadrant coding shows Bangladesh's batters played 71 percent of their shots in that phase into sectors three and four — the cover and point arc. In other words, the zone they leave and the zone they hit into sit on the same side. Seventy-one percent of shots into a single arc means the fielding captain has no decision to make. When the captain has no decision to make, the bowler keeps the freedom to change length.

From the bowling side the picture is clean. With the new ball at Mirpur, the spread of Bangladesh's pacers' line and length — I call it vertical compactness, the variance in height from release to contact — averaged 21 centimetres across the last three matches. For opposition pacers it was 14 centimetres. A larger spread should, in theory, favour the bowler, because the batter cannot estimate length. At Mirpur the opposite is happening: unable to estimate length, Bangladesh's batters leave the ball, and leaving the ball means losing strike.

The spin calculation is subtler. When dew falls in the second innings, spinners' line-and-length accuracy drops — but it does not drop evenly. My coding shows that spinners who bowl primarily on an off-stump line lose 18 percent accuracy; those who bowl stump-to-stump lose only 6 percent. The reason is that a wet ball slides less when it lands on the stumps and more when it lands outside. The bowling plan in the second innings should therefore change completely — yet in my sample Bangladesh changed it in only one match.

The precedent table matters here. Before endorsing any trend I want evidence from three prior matches, and that table does not merely predict — it remembers. In Russia, the precedent table did not predict; it remembered. My Mirpur table holds three entries: first, the 2026 World Cup Super Eight match against Afghanistan, where after two powerplay wickets the strike rate fell to 98; second, the BPL 2026 final, where in the second innings the post-dew spin phase never produced more than six runs an over; third, the most recent bilateral series opener, where losing the toss and batting first produced 34 for two in the powerplay. All three entries share one structure — wickets first, runs later.

The BPL auction variable cannot be excluded either. Fortune Barishal won back-to-back titles for a specific reason — they bought batters whose core skill sits between overs seven and fifteen, outside the powerplay. Yet in the national setup those same batters are pushed up into the powerplay. That is not a selection problem, it is a role-allocation problem. A batter who succeeds at number four in franchise cricket, asked to open internationally, has had his zone map cancelled.

The First Six Overs at Mirpur: Bangladesh's Powerplay Is Really a Twelve-Zone Ledger

Contrarian Angle

Everyone says the powerplay is Bangladesh's core problem. My coding says the powerplay is not the problem — the problem is that the powerplay's decisions are being paid for in overs seven to eleven. If wickets did not fall in the powerplay, that 104-strike-rate phase would not exist.

The second contrarian angle is more uncomfortable. Conventional wisdom says dew in the second innings eases batting, so the chasing side is ahead. In my 216-ball sample at Mirpur, dew is roughly neutral on run rate — but the wicket-fall rate rises 11 percent in the second innings. Because although a wet ball degrades spinners' line and length, batters' footwork degrades too. The advantage and the risk rise together, and the risk arrives first. A side that bats first and makes 160 forces the opposition to think in a dew-affected chase — because dew does not mean an easy chase, it means an unstable chase.

The third contrarian angle is methodological. xG-style indices have entered cricket, but those numbers cannot explain in-innings decisions — who left which ball, why, and how the field was set all sit outside the index. I trust the pattern only after I have walked every grid square. The bench sees what the broadcast never shows.

Takeaway

In the next three matches I will verify two things. One, the number three batter's strike rate between overs seven and eleven — if it cannot clear 120, the problem is the role, not the person. Two, the share of spin overs bowled on a stump-to-stump line in the second innings — if that is not 60 percent of total spin overs, the dew plan stayed on paper. Every match leaves a precedent; my job is to file it correctly.

Related Players