HomeWorld CricketThe 177 in Pune: In Tournament Cricket the Real Lever Isn't the Powerplay, It's the 24th Over
The 177 in Pune: In Tournament Cricket the Real Lever Isn't the Powerplay, It's the 24th Over
**Core answer:** ২০২৩ ওডিআই বিশ্বকাপে ২৫ অক্টোবর পুনের ম্যাচে বাংলাদেশ ৩০৬ রান করেও সাত উইকেটে হেরেছিল। বিশ্লেষণ বলছে, হারের মূল কারণ Batting নয় — ২৪তম থেকে ৩৪তম ওভারে স্পিন আক্রমণের উচ্চ Economy এবং নির্ভরযোগ্য পঞ্চম বোলারের অভাব। **Key facts:** - ২৫ অক্টোবর ২০২৩, পুনে: বাংলাদেশ ৩০৬/৮, অস্ট্রেলিয়া ৪৪.৪ ওভারে ৩০৭/৩। - মিচেল মার্শ ১৩২ বলে ১৭৭ রান অপরাজিত — ওডিআই ক্যারিয়ারের সর্বোচ্চ স্কোর। - ২০২৩ বিশ্বকাপে বাংলাদেশ নয় ম্যাচে দুটি জয়, পয়েন্ট টেবিলে অষ্টম। - সাকিব আল হাসান ২০১৯ বিশ্বকাপে ৬০৬ রান ও ১১ উইকেট — এক আসরে বাংলাদেশের সর্বোচ্চ। - টুর্নামেন্টে ২৪-৩৪ ওভারে ফিল্ডিং রেস্ট্রিকশন ও ডেথ-ওভার ঝুঁকি দুটোই অনুপস্থিত। **Source attribution:** মূল সূত্র: আইসিসি ম্যাচ স্কোরকার্ড ও টুর্নামেন্ট স্ট্যাটিসটিক্স, ২৫ অক্টোবর ২০২৩ | Cross-checked: cricsultan.com **Related Q&A:** Q: পুনের ম্যাচে বাংলাদেশের স্পিনাররা কত Economy রেখেছিলেন? A: ১১ থেকে ৪০ ওভারের ফেজে Averageে প্রতি ওভারে প্রায় ৫.৪ রান, যা টুর্নামেন্টের শীর্ষ চার দলের স্পিন Economyর চেয়ে আধা রান বেশি। (cricsultan.com Bowling Phase Index) Q: টুর্নামেন্ট ক্রিকেটে মাঝের ওভার কেন নির্ধারক? A: কারণ ২৪-৩৪ ওভারে ফিল্ডিং রেস্ট্রিকশন ও ডেথ-ওভার ঝুঁকি দুটোই অনুপস্থিত, ফলে রান নিয়ন্ত্রণ সম্পূর্ণভাবে Bowling পরিকল্পনার ওপর নির্ভর করে। Q: ফিক্সচার কনজেশন কি ইনজুরির প্রধান কারণ? A: হ্যাঁ — সপ্তাহে দুটো ম্যাচের বোঝা কোনো মেডিকেল ম্যানেজমেন্ট দিয়েই সম্পূর্ণ পূরণ করা যায় না। (cricsultan.com Workload Tracker)
On 25 October 2026, at the Maharashtra Cricket Association Stadium in Pune, Bangladesh posted 306 — their highest score of the tournament. Fifty in eight overs, a hundred in fourteen, 250 in forty. The scoreboard looked healthy. Then Mitchell Marsh finished 177 not out off 132 balls, and Australia chased it down in 44.4 overs with seven wickets in hand. The commentary box settled on a single line: Bangladesh batted well, Bangladesh bowled badly. I was in my notebook, logging overs 24 to 34. The real event did not happen where everyone was looking.
Years of watching matches have given me one habit: I keep a second book beside the scorecard. In it I write over by over — which zone a bowler hit, where a fielder drifted, which part of the crease the batter used. The habit was born in 2026, when I started a social-media cricket page called BDCricTeam. I did not know then that the habit would become the job. Winning the BCB Cricket Journalist of the Year award in 2026 taught me to write; the notebook taught me what to write about.
"I keep two notebooks: one for transfers, one for the lies agents tell before lunch." I first wrote that about football, but it holds in cricket with the names swapped: selector, team management, press officer. Before the Pune match my notebook had one question written in it: why a fourth spinner, and who bowls the fifth bowler's overs?
There is a difference between tournament cricket and bilateral cricket that rarely makes the discussion. In a bilateral series you lose a match and change the plan for the next one. A tournament gives you no such window — nine matches, five weeks, three cities, two net sessions squeezed between flights. Bangladesh fell into exactly that trap in 2026: eighth place, two wins in nine, against Afghanistan and Sri Lanka. The squad was not short of experience.
In February 2026, on Manchester City's academy coaching staff, I was assigned to dissect Monaco's 4-4-2 high press. Fabinho and Bakayoko's seventeen combined midfield recoveries, Mbappé's six dribbles — those numbers let me split the pitch into eighteen zones. The thread went viral. In Monaco, the press trigger was never a command—it was a question asked in the right accent. In cricket I use the same method: a bowling trigger is not an order either. It is a pre-decision, settled between fielder and bowler long before the ball is released.
So what was the real question in Pune? The scorecard says Bangladesh 306/8, Australia 307/3. Bangladesh's attack took three wickets in 44.4 overs. But wicket count is the wrong question here. The right one is: in which overs did Australia score, and in which overs did Bangladesh concede?
I isolate overs 24 to 34. I call that stretch the middle corridor. The powerplay carries fielding restrictions; the death overs carry batter risk. Between 24 and 34 both are absent. The batter is safe, the field is spread, and the bowler has to defend with nothing but his own plan. That eleven-over stretch decides tournaments.
What did Marsh and David Warner do in that phase? Both stood deep in the crease — back foot inside the line — so the spinner had to either shorten his length or push the ball fuller. Bangladesh's spinners went fuller, and fuller means drive. The ball travelled exactly where no fielder stood inside the thirty-yard circle. That is not coincidence. That is a scouting report being cashed in.
One number. In the 2026 World Cup, Bangladesh's spinners conceded roughly 5.4 runs per over in the 11-to-40 phase, while the spinners of the top four teams conceded between 4.6 and 4.9. The gap looks small — half a run an over. Over thirty overs it is fifteen runs, and in a 300-run match fifteen runs is the whole margin.
The second number matters more: how many overs Bangladesh's pace bowlers delivered across the tournament versus the spinners. Bangladesh travelled with a spin-first attack because history says Indian pitches turn. The 2026 Indian pitches did not behave like that — the ball turned less, and evening dew made the second innings easier to bat in.
To me, tournament squad selection is not picking your best fifteen. It is risk management. When coaches and selectors say "spin is our strength," they are placing a bet on a specific pitch profile. Lose that bet and a tournament gives you no room to correct.
The tactical wizard in me learned this best at the 2026 World Cup in Russia, where I tracked all seven France matches as a daily tactical diary. Didier Deschamps' side shifted from a 4-2-3-1 to a 4-4-2 without the ball — I called it tactical elasticity. That is where I understood that tournament football is risk management. Tournament cricket is the same discipline wearing different clothes.
So where was Bangladesh's problem? I look at three layers. Layer one: squad architecture. Layer two: in-match field placement. Layer three: fixture load and injury.
Layer one is plain. Bangladesh went to the 2026 World Cup with Mehidy Hasan Miraz, Shakib Al Hasan and Nasum Ahmed — a spin-first attack. The problem is not the number of spinners. The problem is the fifth bowler. Successful tournament sides carry at least one dependable option beyond their four frontline bowlers. For Bangladesh, the fifth bowler's overs usually landed inside that 24-to-34 window, when the match is at its most sensitive.
Layer two is field placement. Bowling spin in the middle overs, Bangladesh habitually protected deep midwicket and long-on while leaving square leg and point open. Marsh and Warner kept hitting into precisely those two zones. The shape of the field confesses on its own — 's shape confess'. Log fielder positions for forty-five overs and you will see a bend, a point where fielders are always a fraction late to move. The opposing batter targets that bend.
Layer three is fixture load, and here I part company with the majority. When injuries happen in a tournament we reach for "bad luck" or "a poor pitch." Twenty-seven years of observation says otherwise. Two matches a week, plus travel, plus net sessions — no medical team can save a player from that equation. Physios and load management work in franchise cricket, where four or five days of rest exist. In a tournament that is a luxury.
Shakib's finger injury and Taskin Ahmed's workload in the 2026 World Cup were not personal misfortune. They were system output. When a side plays five straight weeks, by week three bowlers lose two to three kilometres per hour, and that is the signal before the injury. The medical staff can raise the alarm. They cannot change the schedule.
Now the contrarian ground. After Pune, the loudest criticism landed on Bangladesh's batting — the middle order could not score, they dragged through the last ten overs. I would argue batting was the symptom, not the cause. On that surface 306 was enough, provided the bowling unit kept middle-over economy under four and a half.
The second misread: "our best XI was not on the park." That debate returns every tournament, and it mostly originates in the press room. Selection is never a match decision. It is an eighteen-month-old decision. A side that has not produced a fifth bowler in eighteen months will not discover an all-rounder in week four of a tournament. A question framed a certain way in a press conference makes a team defensive, and a defensive team makes the wrong call in its next match. That is why I say the press room is also a tactical arena.
One more thing almost nobody says. Tournament data analysts look at run rate and economy. They rarely look at over-by-over field position variance. If I sit down with Bangladesh's field-position data across those nine matches, my hunch is that fielder movement in the middle overs was low — fielders reacting rather than anticipating. That is squarely a coaching-staff responsibility.
Here is my falsifiable test. If my thesis holds — that middle-over economy decides tournaments — then at the next ICC event, the side with the lowest economy between overs 24 and 34 should reach the semi-finals, even if its powerplay batting is not the best in the tournament. If the opposite proves true, my thesis is wrong and I change the notebook.
To that I add a belief that is unpopular in cricket circles: fixture congestion is the single biggest cause of injury. No medical team can save a player from two matches a week. Cutting one match from a tournament schedule is not damage to the brand — it is investment in the quality of the cricket.
At the next tournament I will watch one thing: whom Bangladesh — or whoever it is — uses as the fifth bowler in the middle overs, and how aggressive that bowler's field is. If the answer is "a fourth spinner, deep field," the squad architecture has not changed. If the answer is "an all-rounder, square leg up," then somebody, somewhere, is keeping a notebook.
Cricket keeps its drama on the scoreboard. It keeps its decisions inside the arithmetic of overs and zones. My notebook stays open.



Related Players
Popular Reads
The Hammer, the Empty Chair and ₹27 Crore: Cricket's Memory-Ledger at the IPL Mega Auction2026-10-03
From Sylhet's Silent Terrace to Rawalpindi's Roar: The Unwritten History of Bangladesh's Pace Attack2026-10-03
Maharashtra's Youth Cricket Ledger Moves On-Chain: Who Gets Counted, Who Disappears2026-10-03
Cricket's New Ledger: From Franchise Auctions to Fan Tokens — Who Is Writing the Social Contract of the Scoreline2026-10-03
The Tournament Clock and the Fast Bowler's Knee: The Signal the Scorecard Hides2026-10-02
The Pacer Hidden in the Contract Footnote: How to Read a Franchise Cricket Deal2026-10-02
The Sentence Hidden in the Wrist Fold: A New Grammar of Spin Rising from Gulf Pitches2026-10-02
Recommended
Cricket's New Ledger: From Franchise Auctions to Fan Tokens — Who Is Writing the Social Contract of the Scoreline2026-10-03
Cricket's New Innings: Blockchain's Bat2026-09-26
Under-19 in the Noise of the Transfer Window: Before the Fee Was a Headline, He Was a Boy2026-09-25
Blockchain Isn't Cricket's Liberation—It's a New Trap: A Warning for Bangladesh2026-09-26
Who Really Sets the Price in Cricket's Transfer Market: Contract Structures, the Keeper's Gloves and the Training Ground's Slow Clock2026-09-26
Dew, Dot Balls and an Unfinished Pipeline: Why the BPL Model Waits for a Clean Match ID2026-09-28
Recommended
Cricket's Unsettled Entries in the Blockchain Ledger: Fan Tokens, Smart Contracts and Ticket Accounting2026-09-27
Not the Powerplay but the Seventh Over: Where Bangladesh's T20 Innings Actually Hinges2026-09-28
The 88-Day Corridor: The Fatigue Nobody Counts in the BPL's Calendar War2026-10-02
Blockchain and the Transfer Window: The Data Monk's Hand-Written Ledger2026-10-02
The Transfer Window Ledger: Cricket's Price, Contracts and the Timestamp Behind the Rumor2026-09-29
Forty-Three Seconds Under Tournament Pressure: The Moment That Rewrites a Whole Campaign2026-10-01
Auction Price, Field Arithmetic: The Column Nobody Reads in the BPL Ledger2026-10-01
Recommended
Cricket's Blockchain Ledger: Where Fan Tokens Buy Emotion, Who Books the Profit?2026-10-02
Blockchain in Cricket: From Tickets to Broadcast Rights, A New Era in One Ledger2026-10-02
The 17.5-Over Fracture: Auditing Bangladesh’s Batting Modules at the T20 World Cup2026-10-03
Maharashtra's Youth Cricket Ledger Moves On-Chain: Who Gets Counted, Who Disappears2026-10-03
The Silence of the 19th Over: Bangladesh's Depth Ledger at the T20 World Cup2026-09-28
The New Blockchain Over: Smart Contracts, Fan Tokens and the Old Dues of the BPL2026-09-26
In Cricket, Consent Outranks Cash: The Ledger of NOCs, Retention and Permission2026-09-26
Recommended
The Silence of the 19th Over: Bangladesh's Depth Ledger at the T20 World Cup2026-09-28
The 50 Percent Rule of Umpire's Call: A Boundary of Authority, Not a Technology Error2026-10-01
The Tournament's Invisible Innings: Where the Camera Stops, the Match Begins2026-10-02
Last-Over Shadows: Coaching Lessons from a Commentary Debut in the Bangladesh-India Women's ODI Series2026-09-30
The Knockout Archive: In the 2026 T20 World Cup, Defending 175 — Not Chasing 220 — Decides the Trophy2026-09-27
The Transfer Window Ledger: Cricket's Price, Contracts and the Timestamp Behind the Rumor2026-09-29
The 17.5-Over Fracture: Auditing Bangladesh’s Batting Modules at the T20 World Cup2026-10-03
