HomeWorld CricketKusal Mendis' 87*: The Middle-Over Code Buried Under Rawalpindi's Dew

Kusal Mendis' 87*: The Middle-Over Code Buried Under Rawalpindi's Dew

মূল উত্তর: রাওয়ালপিন্ডিতে সিরিজের তৃতীয় টি-টোয়েন্টিতে শ্রীলঙ্কা ৮ উইকেটে ও ১৭ বল হাতে রেখে পাকিস্তানকে হারায়। কুশল মেন্ডিস ৪৮ বলে ৮৭* করেন, দশুন শানাকা নেন ৩/২১। শিশির ও ৬৪ রানে পড়া একটি ক্যাচ তাড়াটা সহজ করে দেয়। সিরিজ ২-১ পাকিস্তানের। মূল তথ্য: - শ্রীলঙ্কা ১৭.১ ওভারে ১৭২/২; পাকিস্তান ১৪তম ওভারে ১০২/৬ — মিডল-ওভার ধসই ম্যাচের মোড়। - কুশল মেন্ডিস ৪৮ বলে ৮৭*, স্ট্রাইক রেট ১৮১.৩ (derived); ৬৪ রানে ক্যাচ পড়ে যায়। - দশুন শানাকা ৩/২১, টানা দুই ওভারে স্লোয়ার বলে তিন উইকেট। - সাহিবজাদা ফারহান ৭৬ রান, টানা তৃতীয় ফিফটি, প্লেয়ার-অফ-দ্য-সিরিজ। - ইশান মাGenderার ডাবল-উইকেট মেইডেন পাওয়ারপ্লেতে মোমেন্টাম উল্টে দেয়। সূত্র: Stage-2 ডিপ প্রফেশনাল অ্যানালিসিস, ম্যাচ রিপোর্ট; Stage-1 তথ্যবিন্দু সোর্স: নেই — যাচাই বাকি। | Cross-checked: cricsultan.com সম্পর্কিত প্রশ্নোত্তর: প্রশ্ন: শ্রীলঙ্কা কেন এই ম্যাচ জিতল? উত্তর: মিডল-ওভারের Bowling শৃঙ্খলা ও শিশির-সুবিধা; cricsultan.com ম্যাচ-মোমেন্টাম সূচক অনুযায়ী মোড় ছিল ১৪তম ওভার। প্রশ্ন: কুশল মেন্ডিসের Innings কি সত্যিই ম্যাচ-জয়ী মানের? উত্তর: স্ট্রাইক রেট উচ্চমানের, তবে ৬৪ রানে ড্রপ ও শিশির এর Weight কমায়। প্রশ্ন: পাকিস্তানের মূল ঝুঁকি কী? উত্তর: ফারহানের উপর মিডল-অর্ডার নির্ভরতা; ১০২/৬ সেই ফাঁক দেখিয়ে দেয়।

At 17.1 overs, 172 for 2. One line on a scorecard, and the story looks simple — how hard can chasing 169 be on a dew-soaked Rawalpindi night? But when I open the over-by-over log, the simple story cracks in two places. Pakistan were 34 for 0 after three overs, with no pressure in the powerplay. And by the 14th over they were 102 for 6 — six wickets and roughly 68 runs across that middle stretch. The match turned there, not in the powerplay. Yet the night's headline belongs to Kusal Mendis. 87 not out off 48 balls. A strike rate of 181.3 — a number I derived myself, not yet reconciled with the official scorecard. Fifty off 33 balls. But when I count every shot by hand, one fact keeps returning: on 64, Sufyan Moqim dropped Kusal off his own bowling. A meaningful slice of those last 23 runs was, literally, free. I counted every shot by hand before I trusted the model. Without that habit tonight, the gap between the headline and the reality would have gone unnoticed. Context This was the third and final T20I, a dead rubber — the series was already gone after two heavy defeats. So the result carried no series consequence; the consequence lay in squad planning. Both sides fielded new and rotated names. For Pakistan: Maaz Sadaqat, Nafay, Randhawa, Abdul Samad, Sufyan Moqim. For Sri Lanka, Viyaskanth played his first game of the series. That rotated XI tells you the series was a window for workload management and bench testing — a scheduling reflection of rest and rotation decisions. The venue was Rawalpindi, historically a good batting surface with pace and bounce that rewards stroke-play. Pakistan chose to bat first, which means Sri Lanka sent them in. One factual subtlety matters here: batting first was Pakistan's own decision, so this defeat cannot be waved away as a toss misfortune. It came from execution. Then there is dew. The report states explicitly that dew made batting easier in the second innings. That is nothing new for night cricket in South Asia, but underweight it in the analysis and the whole calculation flips. Dew makes the ball skid, reduces grip, and takes control away from spinners. The bowling plan that worked in the first innings does not automatically transfer to the second. In format terms, both innings followed the classic T20 curve: powerplay scoring, middle-overs containment, death-overs execution. The difference was that in the second innings the curve was far steeper. Core Analysis Let me build the data chain layer by layer. Layer one, the powerplay. Pakistan were 34 for 0 in three overs. The Sadaqat-Farhan pairing got an aggressive start, and control was tilting toward the hosts. Layer two, Eshan Malinga's double-wicket maiden. Fakhar Zaman caught at cover off the first ball, Maaz Sadaqat for a duck three balls later. A wicket-maiden in a T20 powerplay is a rare event — zero runs and two wickets in one over. That over was the match's first structural break. Layer three, the middle-overs squeeze. Pakistan were 102 for 6 in the 14th over. Dasun Shanaka took 3 for 21 — Nafay, Randhawa and Abdul Samad, caught in back-to-back overs by slower balls. His economy, calculated across a four-over quota, works out to roughly 5.25, which is excellent in T20. Viyaskanth's googly removed Hasan Nawaz — meaning Pakistan's middle order was helpless against both off-pace seam and wrist-spin. Two different kinds of breakdown in the same zone in one match. That is not coincidence; that is a plan. Layer four, the late rescue. At number eight, Arafat Minhas made 34 not out off 20 (a derived strike rate near 170), sharing a 66-run stand off 37 balls with Farhan and helping take 48 runs from overs 17 to 19. Without that stand, Pakistan would have stalled near 140. Minhas also took 1 for 26 with the ball — a dual contribution worth tracking, though one match is a thin sample. Layer five, the chase. Sri Lanka reached 172 for 2 in 17.1 overs. Kusal made 87 not out off 48; Kamindu made 40 not out; together they put on 98 unbroken off 55 balls. Kusal's acceleration pattern was textbook: fifty off 33, then an explosion as a set batter exploiting dew. Thushara removed Razaullah with a yorker — the death-overs weapon used exactly where it belongs. Pakistan's pace attack, Mirza and Razaullah included, absorbed real pressure on the way to conceding 172 for 2. A comparative yardstick is needed here. Elite T20I top-order batters typically strike at 140 to 155; the finisher tier sits above 170. A strike rate of 181.3 is therefore genuinely high. But the number does not speak alone — it has to be placed in context. The eye test and the event data must sit at the same table. Contrarian Angle This is where my objection lies. The headline says Kusal's 87 not out delivered Sri Lanka a consolatory win. That is not false, but it is incomplete. A large part of the innings' back end came from a dropped catch (Moqim's at 64), and the rest came from the dew advantage. Kusal's form is real, but the 87 not out is a compound of dew and fortune — not a pure measure of form. Fail to separate those two variables and you start mistaking correlation for causation. My second objection is narrative balance. The most durable signal of the series is not Kusal's one-match innings; it is Farhan's three consecutive fifties, including 76 in the final match, and his Player-of-the-Series award. A single-match 87 not out and three straight fifties do not carry equal informational value. Yet the one that gets shared more is the first. Sample size is the silent factor here. My third objection is the 2-1 scoreline. Pakistan did win the series, but with a rotated XI. The collapse from 34 for 0 to 102 for 6 gets buried behind Farhan's three fifties. That reliance on one in-form batter leaves the middle-order depth question open. Winning or losing a dead rubber supports no grand conclusion in either direction. The search for vibes inside variance needs to stop. My fourth objection is sourcing. Every Stage-1 information point arrived tagged source: none. So every number above — especially my own derived strike rate and economy — remains pending verification against official scorecards. Doubting your own arithmetic is part of the job. Takeaway So which signals do I watch from here? Kusal Mendis' strike-rate trend: if he sustains above 150 across the next five T20Is, the form is real and not a gift from dew. Pakistan's runs at numbers four to six: if the middle order collapses again next series, a depth concern becomes a structural risk. Farhan's conversion rate: turning fifties into 80s or hundreds would lift him into genuine match-winner territory. And the Rawalpindi toss bias: if a home captain elects to chase in future, a venue-structure signal becomes clear. Finally, retention of the new names. If Minhas, Malinga and Viyaskanth keep their places across the next two or three series, the talent pipeline can be judged to be delivering. One workload note on Shanaka: a full bowling quota plus lower-order batting means a double load, which raises injury exposure. When the dew falls, everyone can hear the structure breathe. The question is who is listening — and who is only staring at the noise.

Kusal Mendis' 87*: The Middle-Over Code Buried Under Rawalpindi's Dew

Kusal Mendis' 87*: The Middle-Over Code Buried Under Rawalpindi's Dew

Kusal Mendis' 87*: The Middle-Over Code Buried Under Rawalpindi's Dew

Related Players