Three Zones of the Death Overs: How Mirpur's Dew Corrupts Bowling Decisions in the BPL Regular Season
core_answer: বাংলাদেশ প্রিমিয়ার Leagueের নিয়মিত পর্বে সন্ধ্যার শিশির ডেথ ওভারের তিনটি Bowling অঞ্চলের ভারসাম্য বদলে দেয়। বল ভিজে গেলে কাটার-নির্ভর ডেক অঞ্চল অকার্যকর হয়ে পড়ে, ইয়র্কার ও ওয়াইড ইয়র্কারের Weight বাড়ে, আর ম্যাচের আসল সিদ্ধান্ত নেওয়া হয় ১৬তম ওভারেই।
key_facts: বাংলাদেশ প্রিমিয়ার League ২০১২ সালে শুরু হয়; সর্বোচ্চ শিরোপার ফাইলে কমিলা ভিক্টোরিয়ান্সের নাম।; লেখকের কোডিং অনুযায়ী ভারী শিশিরের সন্ধ্যায় অঞ্চল ১ ও ২-এ বল পড়ার হার ৪১%-এ নামে, ডেথ ওভারে রান ওঠে ১১.৪-এ।; শুকনো সন্ধ্যায় একই হার ৬২%, ডেথ ওভারে রান প্রতি ওভারে ৭.১।; ডেথ বোলারের Bowling Economy বলের Status দিয়ে নরমালাইজ ছাড়া তুলনাযোগ্য নয়।; ১৬তম ওভারকে লেখক "লুকানো কর" হিসেবে চিহ্নিত করেন, কারণ সেখানেই শিশির ও সেরা বোলারের বণ্টন সংঘর্ষে যায়।
source_attribution: মূল সূত্র: লেখকের নিজস্ব ডেথ-ওভার কোডিং নোট (বিপিএল নিয়মিত পর্ব, টাইমস্ট্যাম্পভিত্তিক ও তিন-ম্যাচ রোলিং এভারেজ); এটি অফিসিয়াল Statistics নয়। League প্রতিষ্ঠার তথ্য: বাংলাদেশ প্রিমিয়ার League, প্রতিষ্ঠাকাল ২০১২।
related_qa: question: ডেথ ওভারে শিশির কীভাবে Bowling পরিকল্পনা বদলায়?, answer: শিশির বলকে ভিজিয়ে দেয়, ফলে কাটার ও ব্যাক-অফ-লেংথ স্লোয়ার পিচে বসে না, তাই বোলারকে ইয়র্কার ও ওয়াইড ইয়র্কারের দিকে সরে আসতে হয়।; question: কেন ১৬তম ওভারকে লুকানো কর বলা হয়?, answer: কারণ হিসাবের খাতায় ওটা মাঝের ওভার, কিন্তু শিশির এসে যাওয়ার পরের প্রথম ওভার হিসেবে সেখানেই ম্যাচের গতি নির্ধারিত হয়।; question: শুধু Bowling Economy দিয়ে ডেথ বোলার বিচার করা কি যথেষ্ট?, answer: যথেষ্ট নয়, কারণ শিশির, ভেন্যু, ফিল্ডিং গ্যাপ ও পরিচালনার মান নরমালাইজ না করলে একই Economy দুই সম্পূর্ণ ভিন্ন পরিস্থিতিকে এক দেখায়।
Fourth ball of the 17th over. The left-arm seamer was hunting a yorker, but water was already running between his fingers before he released. The ball landed on a length instead of the base of the stumps, and the batter sent it straight over long-on. The broadcast graphic will file that as "a six in the 18th over." In my notebook it is something else — a zone lost to dew.
For years I have coded every death-over delivery by location. The database had twelve zones before anyone asked for one. Sitting at the edge of the ground or in front of a screen, I drew those twelve squares, because my first lesson as a coaching staff member was this: praise is vague, location is specific. At the death, only three of those twelve zones decide matches. The rest disappear into the noise of the regular season.
The Bangladesh Premier League began in 2026, and the file with the most titles still carries Comilla Victorians' name. Whatever the league's shape, the regular-season problem stays the same: three matches in four or five days, one evening fixture after another, and one dew question every night.
I do not read it as "an evening match in Mirpur means dew." I code dew as a coordinate. In my file, Mirpur's evening games contain two distinct moments. One is the moment when a spinner can still ask for one more over. The other is the moment the ball is so wet that a seam-up delivery slips out of the hand. What a captain does between those two moments is the real decision of the match.

I split every delivery into three questions: where did it land, which line did it take, and what state was the ball in when it left the hand. Those three questions produce the three death-over zones.
Zone 1 (base): a yorker at the foot of the stumps, landing between zero and one and a half metres from the crease.
Zone 2 (tramline): a wide yorker outside off stump, the delivery that forces the batter to reach.
Zone 3 (deck): a cutter or back-of-length slower ball that grips and climbs, landing one and a half to three metres out.
Everything else that happens at the death is, in my coding, a faulty version of these three. A full toss is a failed Zone 1 attempt. A half-volley is a failed Zone 2 attempt. And the cutters that come straight onto the bat once dew settles are the death of Zone 3.
I coded the death overs of the last three seasons myself, with timestamps and at least three examples per over. What keeps surfacing is bigger than any number: a zone's success depends more on the state of the ball than on the bowler's skill. On a dry ball, Zone 3 works, because the ball grips the surface and breaks the batter's timing. On a wet ball, the same delivery skids through onto the bat, and that is when the long-on sixes start.
My notebook runs a rolling six-over trend, and I write no conclusion without a three-match rolling average. If a bowler puts more than sixty per cent of his 17th-to-19th-over deliveries into Zone 1 or 2 across three straight matches, and that rate does not fall below fifty once dew arrives, his weapon survives a wet ball. Bowlers of that kind are rare in the league, which is exactly why captains burn them in the wrong over.

The precedent table makes me compare three matches together — one dry evening, one with light dew, one drenched. Typically the sample reads like this:
| Sample evening | Dew level | Share of balls in Zones 1 and 2 | Death-over runs per over | |---|---|---|---| | Match one | Almost none | 62% | 7.1 | | Match two | Light | 54% | 8.6 | | Match three | Heavy | 41% | 11.4 |
Those numbers come from my own coding, not an official database. The pattern is nonetheless clear, and the pattern speaks directly to the dew. As dew rises, the weight of Zone 3 falls and the yorker line must widen. A captain who keeps a cutter-reliant bowler on for the 17th over is betting against the dew. A captain who brings on his wide-yorker specialist in that same over is playing the zone.
This is where the venue question enters. In Mirpur, dew arrives late but heavily. The rhythm in Chattogram or Sylhet is different, because humidity and the behaviour of the outfield grass differ. I never forget that difference, because the same bowler, the same delivery, produces two different results at two grounds. If a tactic does not hold at two venues, it is not my tactic, it is my assumption. That is why I never compare death-over run rates in the regular season without a home-away filter.

The bowling side has another weapon that the scorecard never records. At the death I file the gap between long-on and deep midwicket as the silent gap. The runs that leak through it never look like boundaries, but in a three-match rolling average they are the runs that turn matches. The bench sees what the broadcast never shows, and this gap is clearest from the bench.
When I was coding empty-stadium matches in 2026, I began to understand what a death bowler actually trusts. I coded empty stadiums until silence became a coordinate. In a silent ground, bowlers attempted the wide yorker less often, because a mistake would not be buried by noise. A dew match does the opposite: the noise buries the wet-ball error, and the bowler loses his own decision.
There is an uncomfortable point here that is rarely raised in the regular season. We talk about a death bowler's economy rate, when the economy figure is corrupted in exactly the way xG is in football. An 8.2 economy in heavy dew at Mirpur and an 8.2 economy on a dry pitch are not the same object. The number is only an extraction — decision, ball condition, fielding gap and the referee's stoppage rate are not inside it.
The second gap I see is over allocation. Captains save their best death bowler for the 19th over, because that over has the bigger name. My coding says the regular-season match is usually lost in the 16th over — the first over after dew has arrived but before the field has adjusted. I call that over the hidden tax: on the ledger it is a middle over, in reality it is the first step of the death. Holding your best bowler back for the 19th places the 16th-over tax on the shoulders of the other four.
I trust the pattern, but I do not trust it blindly. I trust the pattern only after I have walked every grid square. In Russia, the precedent table did not predict; it remembered. Mirpur's dew is the same — it does not predict, it only remembers who erred in the 16th over.
In the next match I will write down three things: the over in which dew arrived, who bowled the 16th, and how many Zone 2 deliveries that over contained. If those three lines tell the same story three matches running, the question changes. Is dew a weather bulletin, or is it a tactical variable whose contract is renewed every evening?
