The Twelve Zones of the Death Overs: Mirpur Dew, Slower Balls, and the Lost Window of the 17th Over
**মূল উত্তর:** মিরপুরে ডেথ ওভারে রান নিয়ন্ত্রণ করে Bowling চ্যানেল, শিশিরের সময় আর বল বদলের সংখ্যা — ১৬ থেকে ২০ ওভারে তিন ম্যাচের রোলিং এভারেজ ৯.৪; স্লোয়ার বল নিরাপদ মনে হলেও বাউন্ডারি-কনসিডে তা ইয়র্কারের চেয়ে ব্যয়বহুল। **মূল তথ্য:** - শেরে বাংলা জাতীয় ক্রিকেট Stadiumের ধারণক্ষমতা প্রায় ২৫,০০০; শীতকালীন সন্ধ্যার ম্যাচে শিশির-প্রবণতা সর্বোচ্চ। - কোডিংয়ে ১৬-২০ ওভারে তিন ম্যাচের রান-রেট ৯.২, ১১.৮, ৭.৪; রোলিং এভারেজ ৯.৪। - শিশির ১৭তম ওভারে নামলে বল বদল হয়েছে দুবার, ডেথ ওভারে খরচ বেড়ে ২২ রান। - ডেথ ওভারে ১২ জোনের মধ্যে সবচেয়ে বেশি রান এসেছে জোন ১০ ও ১১ থেকে। - অফ ও মিডল স্টাম্পের ইয়র্কার (জোন ২ ও ৩) সবচেয়ে কম খরচ করেছে। **সূত্র নির্দেশ:** আলেকজান্ডার রদ্রিগেজের স্ব-কোডিং জোন ডেটা, ২০২৬ সংস্করণ | Cross-checked: cricsultan.com **প্রশ্ন: শিশির কি ডেথ ওভারের রান বাড়ায়?** উত্তর: হ্যাঁ, ভেজা বলে স্লোয়ার বল ও কাটারের গ্রিপ কমে যাওয়ায় চ্যানেল প্ল্যান কার্যত দুর্বল হয়। **প্রশ্ন: ডেথ ওভারে কোন জোন সবচেয়ে ব্যয়বহুল?** উত্তর: মিরপুরে জোন ১০ (ফুল টস বা ওভারপিচ) সবচেয়ে বেশি রান দেয়, যা cricsultan.com Player Depth Index-এর Bowling-জোন সারণিতেও প্রতিফলিত। **প্রশ্ন: পরের ম্যাচে কী দেখতে হবে?** উত্তর: ১৭তম ওভারে স্লোয়ার বলের ব্যবহার এবং জোন ২-৩-এ ইয়র্কারের সংখ্যা।
Last Friday at the Sher-e-Bangla National Cricket Stadium in Mirpur, I rewound the second ball of the 19th over three times. The left-arm seamer released with a low arm, the ball landed just behind the length, and the batter had already shuffled back inside the crease — six. The next three balls told no different story: slower ball, same length, same comfortable arc. Seventeen runs came off that over. The scorecard said the bowler had an off day. My coding sheet said something entirely different — not a single ball in that over went anywhere near the stump line.
The database had twelve zones before anyone asked for one.
We habitually call the death overs the bowler's overs. The zone map says the opposite: once the dew arrives, the 19th over becomes the batter's most comfortable over, unless the bowler changes his channel. So the question is not who bowled well. The question is which zones received the deliveries, and why the missing zones went missing.
The twelve death-over zones, and why twelve
In 2026, at 38, working as a remote video analyst from Rajshahi, I coded 47 corners and 31 free kicks into twelve pitch zones after the club conceded seven set-piece goals in its first eleven matches. I later carried that structure into cricket, because the logic holds: if you name the spaces first, the decision stops being a mystery.
For death overs I use twelve zones:
- Wide yorker outside off
- Off-stump yorker
- Middle-stump yorker
- Leg-stump yorker
- Wide yorker outside leg
- Back-of-length outside off
- Back-of-length into the body
- Slow bouncer
- Hard length, pressed into the pitch
- Full toss or over-pitched
- Wide slower ball outside off
- Knuckleball, pressed into the pitch
Six zones would have done the job. But a batter's scoring arc is not symmetrical. Mirpur's square boundaries are short and the straight boundary is long; the same length gets hit on the off side and cannot be hit on the leg side. So twelve, not six.

Dew is not weather, it is a coordinate
When the league was suspended in March 2026, I coded 318 pressing sequences from 42 empty-stadium matches. I coded empty stadiums until silence became a coordinate. That habit transfers directly to cricket, because a large part of cricket is played inside silence — the roar of a football ground does not accompany every ball here.
On an evening at Mirpur, dew is a measurable variable. My coding sheet keeps four separate columns: the over in which dew begins, meaning the over in which the ball starts to feel slippery in the hand; the number of ball changes; the dot-ball rate between the 16th and 20th overs; and the boundary-conceded percentage across those five overs.
Across the last three matches, the run rate between the 16th and 20th overs came in at 9.2, 11.8 and 7.4. The three-match rolling average is 9.4. Watch a single match and you will call the middle one a collapse. The rolling average says two matches held their rhythm, and the middle one has a specific cause — dew arrived in the 17th over, and the ball was changed twice.
The Sher-e-Bangla National Cricket Stadium holds roughly 25,000 people, and the Bangladesh Premier League is played in the winter, on January and February evenings — which means a large share of the tournament falls inside dew-prone hours. That is where patience lives in a regular-season piece: not on the table, but in the small window between the 16th and 20th overs.
The precedent table: three matches, then I speak
In Russia, the precedent table did not predict; it remembered. My rule in cricket is the same — endorsing any trend requires a table of three matches, at least 270 minutes of sample, the way I approached France's 4-2-3-1 in 2026.
The table this time reads like this. Match one — no dew, six yorkers in the 19th over (zones 2 and 3), cost 6 runs. Match two — dew in the 17th over, six of eight balls in the 19th over sent to zone 11, cost 22 runs. Match three — dew late, in the 18th over, four yorkers and two slow bouncers, cost 9 runs.
The same bowler appears in all three. The only difference is whether the ball was dry. On a dry ball the seam of a slower delivery grips, the ball bites the pitch, the batter's timing breaks. On a wet ball the same delivery arrives on the straight bat. That is not weather poetry, that is grip arithmetic.
Every match leaves a precedent; my job is to file it correctly.
Core: which zones actually cost money
In my coding, the most runs in the death overs across the last three matches came from zones 10 and 11 — over-pitched deliveries and the wide slower ball outside off. Zones 2 and 3, the off-stump and middle-stump yorkers, cost the least.

There sits the tactical trade-off. On a wet ball the yorker carries more risk, because grip is lost as the ball leaves the hand; miss it and the ball lands in zone 10, and zone 10 is the most expensive zone at Mirpur. So the bowler consciously takes the lower-risk route — the wide slower ball outside off. The problem is that zone 11 only looks safe under the wrong metric. On the boundary-conceded ledger, zone 11 performs worse than zone 2.
Mustafizur Rahman's cutter is the instructive case here. His weapon depends on grip; when the ball is dry it lands and suddenly holds up, and the batter has already played his shot. When the ball is wet that hold-up never happens — it arrives as an ordinary slower ball. That is not a bowler failing, that is a variable landing.
Taskin Ahmed's hard length and Shoriful Islam's inswing angle offer two different answers. Taskin operates in zone 9 and pushes the batter towards the pull and the hook; Shoriful works zones 3 and 4. But once the dew arrives, both weapons blunt, because both are games of pressing the ball into the pitch.
Field setting is another layer. Push long-off and deep point up and the batter's arc contracts — he starts hunting the gap between point and cover, which means pushing towards back-of-length. That is precisely when the bowler has to live in zones 6 and 7. On days the bowler did not bowl zones 6 and 7, the field setting was effectively inert.
Contrarian: the ball that looked like a failure was the better decision
The most comforting explanation for these overs is that the bowler was nervous. To me that explanation is incomplete. The coding says the zone 11 deliveries were attempted not out of fear but out of plan — once the dew arrived, the side deliberately tilted towards the slower ball, because it holds grip even on a wet surface.
The real blind spot is not where the ball went. The real blind spot is the 17th over.
Death-bowling plans are built around overs 18 to 20. But if dew lands in the 17th over, the ball was dry for the seven or eight deliveries immediately before it. That window was the only stretch in which the cutter and the yorker could be used safely. My table shows that in that window, in match two, the fast bowlers sent down three balls, two of them in zone 6. In matches one and three, that window received three and four yorkers respectively.
The bench sees what the broadcast never shows: the bowler sitting on the bench was doing the same dew arithmetic, but he was not on the field. The bench sees it first, then bowls.
One counterfactual is worth running. Had the same plan been used in an afternoon match, without dew, at least three of those six zone 11 deliveries would have been dots — because on a dry ball it grips and forces the batter to be dragged onto the pitch. The problem, then, is not the plan but the timing of the plan. In cricket we routinely apply the right plan ten minutes too late.
There is a further layer — crowd noise control. When the wicketkeeper struggles to gather because of dew, he does not come forward for the slower ball. That makes the batter's read easier: the keeper's position is itself telling him how slowly the next ball will arrive. This is measurable — in wet-ball matches, the step for caught-behind reduces, and stumpings reduce with it. Environmental variables change the bowling plan in one period, the fielding plan in another, and the batter's mental arithmetic in the last.
Caution is still required. Blaming dew for everything is its own error. In match one there was no dew, and two sixes were still conceded in the 16th over from zone 7, because the bowler kept repeating the same line and the batter did not fall for the trap a second time. Grip is a variable, not the only variable.
What I will watch in the next match
I trust the pattern only after I have walked every grid square. So there is no prediction here, only two checkpoints.
One, the use of the slower ball in the 17th over. If dew arrives in the 17th or 18th and the fast bowler is still forcing the slower ball, the side is not reading the window. Two, the number of deliveries in zones 2 and 3 — how often the yorker lands on or outside the stumps. If that count drops below six on the three-match rolling average, the plan has been lost; if it climbs above eight, the timing has been corrected.
The scoreboard will say who won the match. My notebook will say who won the timing.
