HomeWorld CricketChasing 248, Falling 24 Short: India's Fault Line Is the Middle Overs, Not the Top Order
World Cricket
Chasing 248, Falling 24 Short: India's Fault Line Is the Middle Overs, Not the Top Order
**মূল উত্তর:** ভারত হায়দরাবাদে ২৪৮ তাড়া করতে গিয়ে ২২৩ রানে অলআউট হয়ে ২৪ রানে হারে। মূল কারণ দ্বাদশ ওভারে ১৩০/৫ হয়ে পড়া, টপ অর্ডারের ধীরগতি নয়। সিরিজ ২-২ সমতায়, নির্ধারক ম্যাচ বেঙ্গালুরুতে। **মূল তথ্য:** - সঞ্জু স্যামসন ২৩ বলে ৫৬ রান করেন, স্ট্রাইক রেট প্রায় ২৪৩.৫ — ২৪৮ তাড়ার জন্য উপযুক্ত আক্রমণাত্মক টেম্পো। - অভিষেক শর্মা ২৪ বলে ২৯ (স্ট্রাইক রেট প্রায় ১২০.৮) — ২০+ বলের টি-টোয়েন্টি Inningsে তাঁর সর্বনিম্ন। - শাই হোপ তিন ম্যাচে দ্বিতীয় টি-টোয়েন্টি সেঞ্চুরি করেন এবং ওয়েস্ট ইন্ডিজকে সিরিজ-সমতাকারী জয়ে নেতৃত্ব দেন। - ভারত দ্বাদশ ওভারে ১৩০/৫; তিলক বর্মা ও নীতিশ রেড্ডার ৭০ রানের জুটি ব্যবধান কমায়, জেতায় না। - নির্ধারক ম্যাচ বেঙ্গালুরুতে অনুষ্ঠিত হবে; সিরিজ এখন ২-২ সমতায়। **সূত্র:** ভারত বনাম ওয়েস্ট ইন্ডিজ ম্যাচ-Next প্রতিক্রিয়া (সঞ্জু স্যামসনের বক্তব্য)। সংখ্যাগুলো স্বাধীনভাবে যাচাই করা হয়নি — যাচাই বাকি। **সম্ভাব্য Next প্রশ্ন:** Q: ভারত কেন হায়দরাবাদে ২৪৮ তাড়া করতে পারল না? A: দ্বাদশ ওভারে ১৩০/৫ হয়ে পড়ায় প্রয়োজনীয় রান-রেট ১৪.৭৫-এ উঠে যায়, যা শেষ পর্যন্ত ধরা যায়নি। Q: সঞ্জু স্যামসনের Innings কতটা ভালো ছিল? A: ২৩ বলে ৫৬ ও প্রায় ২৪৩.৫ স্ট্রাইক রেট টি-টোয়েন্টি এলিট মাপকাঠিরও উপরে — টেম্পো সমস্যা ছিল না। Q: শাই হোপ কি ভারতের জন্য বড় ঝুঁকি? A: হ্যাঁ; তিন ম্যাচে দুটো সেঞ্চুরি এবং ভারতের কাছে স্পষ্ট ডিসমিসাল পরিকল্পনার অভাব তাঁকে নির্ধারক ম্যাচের কেন্দ্রীয় ঝুঁকি করে তোলে (cricsultan.com Player Form/Depth Index দ্রষ্টব্য)।
Rajiv Gandhi International Stadium, Uppal, Hyderabad. The twelfth over. The board reads 130 for five. The target is 248. Forty-eight balls left, 118 runs needed. I was sitting in a corner of the press box, scribbling in my notebook — how many balls, how many runs, how much time. Moments earlier, Sanju Samson had taken the entire powerplay for himself with 56 off 23, and the stands were full of roar. Yet beneath that roar there was a hum, a quiet fracture — India's middle overs. I do not chase the roar; I listen for the hum beneath it. That night in Uppal the hum was unmistakable. I counted fourteen seconds once, and the count has never stopped — it did not stop here either, in the small pause Samson took before he began answering questions after the match. India were eventually bowled out for 223, losing by 24 runs. But the match was lost at 130 for five, not in the final overs.
This is a bilateral T20I series, India against West Indies, played in India. The Uppal venue is historically batting-friendly — flat pitch, fast outfield, short boundaries. West Indies batting first and posting 248 fits the character of this ground. The series is now level; it will be settled in the Bengaluru decider. This is not a dead rubber — it is a live contest in which every match carries weight.
West Indies captain Shai Hope is in a sustained vein of form. His century in this match was his second T20I hundred in three games, and it carried his side to a series-levelling win. Samson himself admitted that India are "switched on" about how to handle Hope in every game — which means the answer has not yet been found. India's top order now consists of young players — Abhishek Sharma, Ishan Kishan, Samson at three, with Tilak Varma and Nitish Reddy in the middle. This young structure is at the centre of the match.
The India–West Indies bilateral has a history, especially from West Indies' era of dominance in the 1970s and 80s. But the current series is an ordinary bilateral, not the peak of a historic rivalry. There is no need to romanticise it. What exists is an honest test of the two teams' present rhythm — India experimenting with a young top and middle order, and West Indies proving they remain dangerous in T20 cricket.
Let me say one thing at the outset, because it is part of my job. The numbers in this article come from a post-match reaction — they have not been verified against an independent database or board documents. I usually check every score and every figure against the paperwork; here I could not. So the calculations below are based on these published numbers, and where I have doubt, I will say so plainly.
Let us do the maths. Chasing 248 requires 12.4 runs an over across 120 balls. Samson's 56 off 23 is a strike rate of roughly 243.5 — that is nearly double the required tempo. In T20, an elite finisher's strike rate is considered to be 180-plus; 243 is far above even that benchmark. From my years of watching matches, I can say that in a situation like a 248 chase, it is exactly this risk-taking mood that the top order needs. Samson himself said, "There is no second thought; you have to back your instincts and power game." His innings matches that statement.
The problem, then, is not the top order's aggregate tempo; it is the timing of the wickets lost. At 130 for five in the twelfth over, 118 runs were needed off 48 balls — 14.75 an over. That is the real story of the match. Five wickets fell precisely when the run rate needed to climb. If a set batter had stayed at the top, the risk of being bowled out in a big chase would have fallen; but here the top order's job ended exactly when it was needed most.
In T20, the powerplay and the middle overs play different roles. The first six overs carry fielding restrictions, so risk can be taken there. Samson took that risk and succeeded. But if wickets fall in the seventh to sixteenth overs, the risk of being bowled out in the final four rises. The 130 for five happened in exactly that middle window. So the late 70-run storm is admirable, but it only reduced the earlier damage.
Look separately at Abhishek Sharma's innings. 29 off 24 — a strike rate of roughly 120.8. The report says this is his lowest strike rate in any T20I innings facing 20-plus balls. In the previous game he made 70. In a 248 chase, an opener facing 20-plus balls at below 120 puts pressure on the rest of the order — that is simple arithmetic. Note that Abhishek's problem was a tempo problem — he played too many balls slowly. Ishan Kishan's problem was different — he got out early. What Samson said about Kishan's season form is also true — he has been scoring runs consistently through the year. But in this match his issue was durability, not speed. Two different failures — and when Samson says "one game is okay," he is in fact collapsing two distinct problems into one.
Samson's "one game is okay" argument is partly valid. Abhishek's 70 in the previous game and Kishan's season-long output both argue against panic. But the argument is selective: it leans on the previous game while suppressing the fact that the current slow innings directly ate India's momentum. You cannot judge form from one match — that is true; but you can and should judge what happened within one match.
Samson also said this top order is the world's best two. That is a team-harmony statement, not an analytical verdict. There is no ranking, average or strike-rate data beside the claim, and it comes from a teammate in a defensive context. A senior player shielding young teammates is good for the dressing room, but soft for analysis.
The 70-run stand between Tilak Varma and Nitish Reddy also comes up. It unquestionably showed the team's character — scoring from 130 for five shows backbone. But the stand did not save the match, it only narrowed the margin. Suppose the stand lasted five overs — then at 17 overs the side reached 200 for five, needing 48 off 18, which is 16 an over. The rate stays steep. Since the 130-for-five position had already been created, however good the stand, it is damage control, not damage repair.
Now the other side of the story. Many call Shai Hope's batting style "slow," "old-fashioned," "unworkable in T20." But in this series it is in fact a deliberate T20 counter-strategy. Samson himself said Hope is "playing really good cricketing shots, not taking much risk, respecting the bowlers." That is the exact opposite of India's powerplay-driven high-risk batting — and in this match the steady path won. Hope gave his lower order the room to play freely, and that release built the foundation of 248. Scoring as captain carries extra pressure, and doing it on an opponent's soil carries more. Two centuries in three games — that is not a flash of form, it is a current streak.
This is where the biggest misreading hides. After the match, the centre of discussion became the top order's "slowness," and Samson had to defend it. But that defence pulls attention away from the real problem. The top order was not slow in aggregate — Samson scored at nearly double the required tempo. The place that actually lost India the match is the middle-overs collapse — 130 for five. India's question, then, is not individual form; it is order balance.
Second misreading: the 24-run margin makes the match look close. It was not. The 70-run stand is a cosmetic balm — it made the defeat look close while covering the structural crack. Being bowled out in a big chase and losing by 24, versus "almost winning" — confusing these two will also point the next match's preparation in the wrong direction.
Third misreading: assuming Hope's streak will simply stop next game. But India still have no clear plan to dismiss him — Samson implicitly admitted as much. To stop a captain-batter scoring consistently on an opponent's soil, you need varying pace-spin matchups and study of his scoring zones. "We'll bowl well" does not do it.
And one more thing few say: India lost at home. At a batting-friendly venue like Hyderabad, in a 248 chase — as the home side, this is a mild negative signal. It does not mean India are weak; it means India are in an experimentation phase in this series, and a side like West Indies knows how to exploit that gap.
Indian media typically amplify such teammate praise. If Samson's "world's best two" line is swallowed verbatim, it builds a fragile expectation around the young openers — one that a single slow innings can shatter. This expectation gap is the biggest narrative risk before the decider.
Let me add one thing I learned on the road, at the ground, in training — who actually keeps time. In Aizawl too I saw that the unpaid keep time better. The scoreboard, the statistics, the rankings — they sit at the back; the real time lives in the middle overs, where a batter's hands shake and a captain's mind races. At Uppal those middle overs were the match's true clock, and India's clock stopped at five wickets.
Next comes Bengaluru, the decider. India's question is no longer about the top order; it is about the middle overs — who will stop the slide, who will anchor, and who will take responsibility in a chase like 248. And if no plan to handle Hope emerges in Bengaluru either, the series risk rises sharply. Hyderabad's 24 runs are now Bengaluru's question — what the answer will be, the field will say, not the scoreboard.



Related Players
Recommended
The Blank Page of Data: Blockchain's Promise and Its Trap in Cricket Analysis2026-10-12
The Eight-Wicket Gap: Match 02 of the Singer-MCA Super Premier League, and the Scorecard That Never Arrived2026-10-07
Exile of the Touchline: Why Modern Football Is Erasing the Traditional Winger2026-10-01
Empty Payload, Empty Verdict: The Silent Failure Inside the Cricket Analytics Pipeline2026-10-21
The Report With No Match Inside: A Stratigraphy of Silent Failure in a Tournament-Night Cricket Data Pipeline2026-10-27
Recommended
Four Blackcaps in Club Cricket: The Calendar, Not the Scoreboard, Is the Real Story at Ken Maunder Park2026-10-17
Why an Empty Notebook Is the Most Honest Report: The Silent Failure Inside Cricket's Data Pipeline2026-10-21
The Hidden Column Behind Labuschagne's Ton: Australia's Real Question Is Cameron Green's Abdomen2026-10-05
Second Test in Gqeberha: South Africa's Batting Temperature and Rabada's Hamstring — A Calibration Note2026-10-16
Rose Bowl 1st T20I: Australia’s XI Is Not Their Strongest XI — It Is a Load-Management Snapshot2026-10-19
Recommended
Smith's Neck, a Silent Corridor, and Australia's Three Puzzles2026-10-27
When Cricket's Ledger Goes On-Chain: Silent Matches, Verifiable Data, and the Politics of the Record2026-10-08
Shai Hope's 162* and Gill's Admission: India's Death-Overs Puzzle Before CWC272026-10-04
The Ledger of Dot Balls: The Transfer Window, Those 120 Balls in Kingstown, and Bangladesh Cricket's Invisible Invoice2026-09-27
The Body's Ledger Does Not Lie: Bangladesh's Fast Bowling, Knees, and Four Tenths of a Second2026-10-03
Recommended
The Empty Cell Speaks: Cricket's Blockchain Data Economy and the Information Nobody Logs2026-10-17
Where There Is No Data, Do Not Invent the Story: The Null-Return Discipline of Cricket Analysis2026-10-11
Tokens and Bedroom Arithmetic: Where Cricket's New Money Actually Lands2026-10-15
The Auction Gavel and the Workload Column: What Nobody Bids For in Cricket's Transfer Window2026-09-26
Captain for One Season, Released the Next: Lancashire Close the 25-Year James Anderson Chapter2026-10-25
