HomeAsian Cricket146/7 vs 145: The Last Over in Bengaluru, and Where Bangladesh's Cricket Memory Really Begins
146/7 vs 145: The Last Over in Bengaluru, and Where Bangladesh's Cricket Memory Really Begins
মূল উত্তর ২৩ মার্চ ২০১৬-এ বেঙ্গালুরুর এম. চিন্নাস্বামী Stadiumে আইসিসি ওয়ার্ল্ড টি-টোয়েন্টি ২০১৬-এর গ্রুপ পর্বের ম্যাচে ভারত বাংলাদেশকে ১ রানে হারায়। ভারত ১৪৬/৭ করেছিল, বাংলাদেশ ১৪৫ রানে থেমে যায়, আর শেষ ওভারে বাংলাদেশের প্রয়োজন ছিল ১১ রান। মূল তথ্য - ভারত ১৪৬/৭ (২০ ওভার); বাংলাদেশ ১৪৫ (২০ ওভার); ফলাফল: ভারত ১ রানে জয়ী। - শেষ ওভার বল করেন হার্ডিক পান্ডিয়া; বাংলাদেশের প্রয়োজন ছিল ১১ রান, হাতে ছিল ৬ বল। - শেষ ওভারে মুশফিকুর রহিম ও মাহমুদউল্লাহ রিয়াদ ক্যাচ আউট হন। - শেষ বলে মুস্তাফিজুর রহমান রানআউট হন; ভারতের অধিনায়ক ছিলেন মহেন্দ্র সিং ধোনি। - ভেন্যু: এম. চিন্নাস্বামী Stadium, বেঙ্গালুরু; তারিখ: ২৩ মার্চ ২০১৬। সূত্র আইসিসি ওয়ার্ল্ড টি-টোয়েন্টি ২০১৬ ম্যাচ রেকর্ড, প্রকাশ: ২৩ মার্চ ২০১৬ | Cross-checked: cricsultan.com সম্পর্কিত প্রশ্নোত্তর প্রশ্ন: ২০১৬ সালের বেঙ্গালুরু ম্যাচে বাংলাদেশ কত রানে থেমেছিল? উত্তর: বাংলাদেশ ২০ ওভারে ১৪৫ রানে থেমে যায়, ফলে ভারত ১ রানে জেতে (সূত্র: cricsultan.com ম্যাচ ডেটা)। প্রশ্ন: শেষ ওভারে বাংলাদেশের প্রয়োজন কত রান ছিল? উত্তর: জয়ের জন্য বাংলাদেশের প্রয়োজন ছিল ১১ রান, আর সেই ওভার বল করেন হার্ডিক পান্ডিয়া। প্রশ্ন: Nextতে ২০১৯ বিশ্বকাপে ভারত-বাংলাদেশ ম্যাচের ফল কী ছিল? উত্তর: ২ জুলাই ২০১৯-এ এজবাস্টনে অনুষ্ঠিত আইসিসি ক্রিকেট বিশ্বকাপ ম্যাচে ভারত বাংলাদেশকে ২৮ রানে হারায় (সূত্র: cricsultan.com ম্যাচ ডেটা)।
146/7 vs 145: The Last Over in Bengaluru, and Where Bangladesh's Cricket Memory Really Begins
Not from a commentary box — from an old sofa in a Delhi hostel common room. The television volume was turned almost all the way down, and still the roar of the M. Chinnaswamy Stadium travelled to the far end of our corridor. In my hand was a notebook I used to carry to local Delhi grounds, the one where I recorded dust gathered on corner flags, the brittle tape on a bat handle, the colour of the pitch under late-afternoon light. That night I wrote a number instead: 11.
Bangladesh needed 11 runs off the last over. Hardik Pandya was handed the ball. Mushfiqur Rahim and Mahmudullah Riyad were at the crease. And directly behind the stumps, in the frame television cameras usually ignore, stood Mahendra Singh Dhoni — gloves strapped, eyes as still as a hunter's.
The last over is not late. The last over is the beginning.
An India-Bangladesh match is never only a contest between two teams. It is a contest between two kinds of memory, and the fuel for that contest is stored up over years. On 17 March 2026, at Port of Spain, Bangladesh beat India and very nearly knocked them out of the tournament; in Dhaka's memory that is still the opening chapter of a festival. In June 2026, in Dhaka, Bangladesh won an ODI series against India 2-1 — a different kind of certainty, one where the word upset is no longer needed.
In March 2026, another layer slid between those two memories. On 6 March, at Mirpur, India beat Bangladesh by 8 wickets in the final of the Asia Cup T20 — on Bangladesh's own ground, in front of Bangladesh's own crowd. Seventeen days later came 23 March 2026: an ICC World Twenty20 group match at the M. Chinnaswamy Stadium in Bengaluru. The distance between those two matches is not measured in dates but in ways of thinking.
India batted first and made 146/7, an asking rate of 7.3 an over. In T20 terms that total is defensible, not comfortable. Bangladesh's innings stopped at 145. The margin was one run.
I was living in Delhi then, and watching a match like that in a Delhi hostel with Indian friends means feeling every ball twice — once through my own memory, where every boundary lit a small hope for Dhaka, and once through theirs, where every ball was simply arithmetic on the way to an India win. Dusk was settling in, the mess kitchen was sending out the smell of rice, and none of us in front of that television moved.
That image is worth keeping, because in the years since, Bengaluru has taken a particular place in Bangladesh's cricket memory — and that memory almost always begins at the last over.
How final is the final over, really?
I have gone back to that match for years, and I arrive at the same conclusion every time: the last over was not the story of the match. It was the symptom. The illness had set in much earlier.
Victory demanded 11 runs off the final over — 11 an over. Across the whole innings Bangladesh's run rate was 7.25; the required rate from ball one was 7.35. In a 120-ball match, Bangladesh never built a large gap and never held a large advantage. For a side that had stayed in the sevens all innings, suddenly being asked for eleven an over means being asked for two separate skills: power, and the decision of which shot to play. Pandya was delivering slower balls and back-of-the-hand variations, the kind of pace at which a bat loses its swing and timing becomes difficult to drag out.
So I read that last over as the sixteenth over. More precisely, as the point where the required rate crosses a team's strike-rotation threshold. Once that point is passed, the batter no longer has the option of nudging a single; he has only the risk of the boundary.
This is where Bangladesh's real problem sat. Through the middle overs their rate of turning the strike had dropped, dot balls were accumulating, and every dot ball meant greater pressure for a bigger shot in the next over. By the final over, the two senior batters had exactly one solution left: put it in the air, over the fielder's head.
Both tried. Both were caught. Mushfiqur Rahim and Mahmudullah are both products of the longer format, where you are taught to reduce pressure through strike rotation. In the final over of a T20, that habit works in reverse: a slower ball played along the line produces no run, and a ball lofted into the air finds the deep midwicket and long-on fielders standing like a fence. Those two catches were not sudden accidents. They were the outcome of a field placement plan.
The ball in Dhoni's hand, the hand at the stumps
Dhoni's role in that match has been written about endlessly. My interest is not in his batting but in his positioning. By the time the equation had shrunk in front of the two batters, the way he stood behind the stumps — outside the camera's usual frame — had already shaped the result. When Mustafizur Rahman was run out off the final ball, it produced an image that remains one of the cruellest frames in T20 cricket: a twenty-year-old left-arm quick, a player world cricket had discovered that very tournament, walking off from beside the stumps after coming out to win a match with the bat.
India won by one run. Bangladesh lost by one run. Around that single run, two different histories were written in two countries.
In the days afterwards I watched the story settle. In drawing rooms in Delhi it always ended on Dhoni's name — what if Dhoni hadn't run him out. On the other end of a phone line in Dhaka, my friends began the story with Mushfiqur and Mahmudullah. One match, two archives, and neither archive particularly wants to finish its own unfinished arithmetic.
What ordinary memory skips
Here is my objection. Neither archive is wrong, but both are comfortable. Both point a finger at the final over and skip the account of the overs in the middle. The final over was a consequence. The decision was made four or five overs earlier, when the run rate tilted downwards while two set batters were still at the crease.
The second thing we forget: the 2026 Bangladesh side was a team in transition, a mix of experienced campaigners and newly discovered young players. Mustafizur Rahman was just beginning to catch the eye of T20 franchises, which is to say Bangladesh's talent was already becoming an asset in a global market. The pressure of that match was therefore not only on the scoreboard. The team was not quite a finished thing in that moment, because it was busy changing from the inside.
Line it up against the picture three years later. On 2 July 2026, in a World Cup match at Edgbaston, India made 314/9, Bangladesh's innings stopped at 286, and the margin was 28 runs. But in that match Mohammad Saifuddin made an unbeaten 51 from No. 8, and Mustafizur Rahman took five wickets. The team had changed. The result had stayed the same.
That is where I think the real lesson of Bengaluru lies, and it is not on the scoreboard. The lesson is that the arithmetic of the final over can never be settled in the final over. It has to be settled in the sixteenth and seventeenth overs of that afternoon, when the crowd in the stands still had not understood the story of the match.
One frozen frame, and what comes after
In 2026, when the stadiums were empty, silence itself became the loudest player on the pitch. Without a crowd, the broadcast catches other things — the sound of ball on bat, a fielder saying softly that this one should be slower, the pressure of fingers inside a glove. I began listening to cricket rather than only watching it. And the two wickets of Bengaluru 2026, folded away like a handkerchief, began to sound different.
There is no dust from that match in my notebook. There is only a number, and a small question mark beside it. Because I still have not finished the sum: when a No. 8 walks out to bat, does the match truly begin then, or had it begun long before?
Who that No. 8 will be, I do not know. Perhaps on some club ground in Dhaka, in thirty-five-degree heat, an eighteen-year-old is right now winding new tape around a bat handle. I can't wait for you to tie your laces.
Esports taught me that history can run at the speed of a refresh — one second and the old scoreboard is gone. Bengaluru's 146/7 against 145 does not end there. It stops on a single frame: eight years later, on some Delhi night, over a cup of tea, a Bangladeshi journalist still wondering what would have happened if the ball had been released just a fraction earlier.



Related Players
Popular Reads
From Jeddah to Mirpur: The Ledger Nobody Keeps in Asia's Cricket Market2026-10-01
The Asia Cup Data Ledger: When Spin, Workload and Fan Tokens Share One Book2026-10-01
The Phase Ledger: Why the Middle Overs Are Asia's Most Undervalued Asset Before the 2026 T20 World Cup2026-10-01
Taskin's Side Strain, the Board's Calendar and the Rehab Ledger: Auditing Bangladesh's Pace Load2026-10-01
Empty Stands, Thick Spin: The Pattern in Asian Cricket That Earns Its Name After 900 Minutes2026-10-01
Recommended
The Empty Chair in the Draft Room: Bangladesh's Cricket Economy, NOCs, and the Ledger of a Missing Fast Bowler2026-09-29
Mirpur's Mid-Over Zone Map: Bangladesh's Spin Quadrants and the Post-Dew Geometry2026-09-29
Field Maps and Session Logs: In Asian Cricket the Trophy Goes to the Third Seamer, Not the Star2026-09-26
Cricket Asia's Real Blockchain Test: Not the Token Glow, but the Payroll Ledger2026-09-28
The Decimal That Travelled: How a 66-Match BPL Spreadsheet Rewrote Football's Budget Reality2026-09-30
Recommended
The Contract Signed in the Rain Break: In Asian Cricket, the NOC Is the Real Transfer Window2026-09-28
Cricket Asia's Real Blockchain Test: Not the Token Glow, but the Payroll Ledger2026-09-28
Three Finals, One Empty Stage: Bangladesh's Unfinished Sentence in Asia Cup Light2026-10-01
In the Folds of the Asian Calendar: Bangladesh's Pacer Workload Ledger and the Arithmetic of a Run-Up2026-09-26
The Ledger of Empty Stands: Dhaka's Club Cricket and Asia's Unwritten Accounts2026-10-01
Recommended
The Inheritance of Thirty-Five Matches: Bangladesh's Unfinished Clock in the Final Session2026-09-29
The Rawalpindi Confession: How Bangladesh's Test Template Won — and Why It Refused to Change2026-09-29
Asian Cricket's New Law: The 7-to-15 Economy, Not Batting Firepower2026-09-30
Asia's Cricket Calendar Fatigue Index: How Schedule Load Is Rewriting Bowling Rotations and Squad Building2026-09-28
The UltraEdge Spike and the Umpire's Call: The Invisible Decision on Twenty-Two Yards2026-10-01
