HomeAsian CricketOvers 11–25: Where Asian ODI Matches Are Actually Lost

Overs 11–25: Where Asian ODI Matches Are Actually Lost

প্রশ্ন: এশিয়ার ওয়ানডেতে ম্যাচ আসলে কোন ফেজে নির্ধারিত হয়? মূল উত্তর (৪২ শব্দ): এশিয়ায় ৬৪টি ওয়ানডের ফেজ-ভিত্তিক লগ বলছে, ম্যাচের ভাগ্য সবচেয়ে বেশি নির্ধারিত হয় ১১–২৫ ওভারে। জেতা ও হারা দলের রান রেট ব্যবধান ওই জানালায় +০.৯১, ডেথ ওভারে মাত্র +০.২৮। মূল তথ্য: - ফেজভিত্তিক রান রেট: পাওয়ারপ্লে ৫.৩, ১১–২৫ ওভার ৪.৬, ২৬–৪০ ওভার ৫.৭, ডেথ ৮.৪। - ১১–৪০ ওভারে ২২+ স্পিন ওভার নেওয়া ৩০ ম্যাচের ২১টিতেই সেই দল জিতেছে। - ১১–২৫ ওভারে স্পিন Economy ৪.১২, পেস Economy ৪.৮৩, প্রতি ওভারে উইকেট ০.১৭। - চট্টগ্রামে ১১–২৫ ওভারের রান রেট ৪.০৯, মিরপুরে ৪.৪৪, সিলেটে ৪.৯১। - ৬৪ ম্যাচের ৯টিতে ১১–২৫ ওভার জিতেও শেষ পর্যন্ত ম্যাচ হেরেছে দলটি। সূত্র: xG চট্টগ্রাম ফেজ-ভিত্তিক বল-বাই-বল ডেটাসেট, সংকলন: তামিম খান, সময়কাল ১ জানুয়ারি ২০২৪ – ৩০ নভেম্বর ২০২৫ | Cross-checked: cricsultan.com সম্পর্কিত প্রশ্নোত্তর: প্রশ্ন: এশিয়ার ওয়ানডেতে সবচেয়ে গুরুত্বপূর্ণ মেট্রিক কোনটি? উত্তর: ১১–২৫ ওভারের রান রেট ডিফারেনশিয়াল, কারণ ওই ফেজেই জেতা ও হারা দলের ব্যবধান সবচেয়ে বড়। প্রশ্ন: চট্টগ্রামের পিচ কি অন্য এশীয় ভেন্যুর চেয়ে আলাদা? উত্তর: হ্যাঁ, cricsultan.com Venue Behaviour Index অনুযায়ী চট্টগ্রামের মিডল-ওভার রান রেট সিলেটের চেয়ে ০.৮২ কম, কারণ বল পুরনো হলে ওভেনমেন্ট কমে। প্রশ্ন: এই ডেটা টি-টোয়েন্টিতে প্রযোজ্য হবে কি? উত্তর: আংশিক, কারণ টি-টোয়েন্টিতে ফেজের দৈর্ঘ্য ভিন্ন, তাই ১১–২৫ ওভারের জানালা সরাসরি অনুবাদ করা যায় না, ক্যালিব্রেশন দরকার।

Match number 37 in my logbook, venue Chattogram. Sitting in block three of the Zahur Ahmed Chowdhury Stadium, I was counting the last ten overs — 94 needed, seven wickets in hand. Someone two rows away said the real match starts now. The scorecard later said the hosts lost by four runs, needing 14 off the final over. Back home, I turned to the rear page of my notebook: overs 11 to 25, 90 balls, 48 runs, three boundaries. The match was lost in that silent window, while the crowd was nearly quiet and the cameras were pointed at the dugout. The final five overs were an epilogue; the story had already been written. The question is simple — in Asian ODIs, which window actually decides the match, and why do we keep staring at the wrong one?

This piece rests on 64 one-day internationals played in Asia between January 2026 and November 2026. I split every ball into four phases — powerplay (1–10), the second window (11–25), the third window (26–40) and the death (41–50) — and tracked run rate, boundary percentage, dot-ball pressure (the ODI cousin of football's PPDA, meaning how many deliveries per over force the batter to defend) and the number of spin overs. I controlled for pitch type, dew, day-night conditions, toss and venue, because in Asian conditions an uncontrolled variable turns every conclusion into coincidence.

A confession about method. I built xG Chattogram because the Chattogram league table was lying in plain sight. Official scorecards still flatten an innings into a single average run rate. 48 off 90 balls becomes '3.2 an over', and the card never mentions that boundary percentage had collapsed to 7.2, that strike rotation had jammed, that the middle order was defending 34 percent of deliveries on its own end. The 64-match spreadsheet was not a prediction; it was a confession of what I could not stop counting.

Overs 11–25: Where Asian ODI Matches Are Actually Lost

Here is the phase picture, runs per over and boundary percentage: powerplay 5.3 / 11.8; overs 11–25: 4.6 / 7.2; overs 26–40: 5.7 / 9.4; death overs 8.4 / 14.6. None of this is news. The news is in the internal differential. The biggest run-rate gap between winners and losers opens in overs 11–25 (+0.91); the smallest gap sits in the death overs (+0.28). We spend hours arguing about death bowling, finishing and nerve in a phase where the two teams separate least, and ignore the phase where they separate most.

Spin sharpens the effect. In the 30 matches where a side bowled 22 or more spin overs between overs 11 and 40, that side won 21. In the same phase, spin economy was 4.12 against pace's 4.83. Dot-ball pressure points the same way: winning sides forced 3.4 dots per over in the window, losing sides 2.6. The reason is not mysterious. On slow or damp surfaces the ball stops, and a batter who wants runs must take the risk himself — and wickets fall fastest here, 0.17 per over, nearly double the powerplay rate.

Split by venue, Chattogram becomes a variable in its own right. In my log the 11–25 run rate is 4.91 in Sylhet, 4.44 in Mirpur and 4.09 in Chattogram. The scoreboard goes quiet right in the middle in Chattogram, yet the last ten overs there still produce more than eight an over. That gap is the pitch's character: as the ball ages, the shine and the carry go, and then dew rewrites the hand-ball equation. Anyone dropping a Chennai or Colombo model straight into Chattogram without controlling context gets an output I do not trust.

Player patterns confirm it. When Afghanistan gives Rashid Khan and Mohammad Nabi long spells in the 11–25 window, the scoreboard nearly freezes — a pattern my notes keep returning to. Sri Lanka plays the same game through Wanindu Hasaranga's wrist. India's Axar Patel and Kuldeep Yadav pairing refuses to let the middle order leave the crease, and Bangladesh's control through Mehidy Hasan Miraz and Shakib Al Hasan is built for exactly this phase. Reading innings by Towhid Hridoy or Najmul Hossain Shanto, the strike rate gap between the 11–25 window and the death overs is wide — that is not a finishing failure, it is a phase-management failure.

Here I have to argue against my own model. Correlation is never causation. Sixty-four matches is a small sample, and my framework is calibrated on ball-tracking from Chattogram and Mirpur, which may not travel to Colombo or Kandy. I logged dew separately, yet the third window behaves differently in 31 day-night matches than in day games, and that was never fully controlled. Counter-examples exist too: in nine matches in my log, the side that won the 11–25 window lost the game. The window is a necessary condition, not a sufficient one. One extraordinary innings or a toss under cloud can invert the whole table — which is why I use this as a question, not a claim.

There is a layer bigger than the data. In 11 of the 64 matches, a major DRS call landed inside the 11–25 window and changed the phase's trajectory. Stadium screens show only the verdict, never the reasoning. Twenty-five thousand people watch the decision but not the argument; television commentators guess, and the fan is left to reconstruct the logic alone. Everyone talks about transparency, yet the crowd inside the ground remains the ignored audience. That information gap also leaves a hole in my own dataset: no scorecard records how many runs a wrong decision saved or cost.

Overs 11–25: Where Asian ODI Matches Are Actually Lost

One thing I can state without hedging. Overs 11–25 are where the scoreboard goes quiet while the game does not. Strike rotation, left-right partnership rhythm, five degrees of field placement shifting — all of it is settled there. If you track only one metric across the first three matches of any series, make it the run-rate differential in this window; the rest of the series will start explaining itself. In 13 years of watching, that is the habit that has paid most — the notebook fills up long before the final five overs.

The Data Monk does not worship numbers; he interrogates them until they confess context. When the stadiums emptied, the numbers did not go quiet; they changed their accent. So the question is no longer about a finisher's bio-data. The question is who walks in at the start of the 11th over and turns 90 balls into 60 runs, so that the death overs even matter. Until selection is made out of fear of the last five overs, we will keep staring at the wrong window.

Related Players