From 120/1 to 222: Liton's Century and the Lesson of Bangladesh's Unfinished Innings

At the Dubai International Stadium on 28 September 2026, the floodlights were white, but the sound in the stands was green and red. Sitting in the Rajshahi press box, I had a phone in front of me and headphones over my ears, yet my eyes were fixed on one pair of legs — Liton Das's. That night he made 121 off 117 balls, the highest score by a Bangladesh batter in an Asia Cup final. Forty-three balls still remained, yet the team stopped at 222. I typed one line into my phone: a man can build an innings, a team cannot. That line keeps returning, because the night in Dubai was more than the story of a final. It was an X-ray of Bangladesh's ODI batting structure, and the fracture was plainly visible.

Bangladesh arrived at the 2026 Asia Cup under Mashrafe Bin Mortaza with a clear template. The plan was simple: one batter anchors the innings, the rest score around him, and the bowling attacks in the last ten overs. In the group stage against Sri Lanka and Afghanistan it worked; in Dubai against Pakistan it hardened. In the final, Bangladesh met the template's limit for the first time, at the moment when the opponent was India and the stage was the largest.

One fact deserves to be remembered, because it is usually lost in the discussion. Bangladesh reached that final without two frontline batters. Tamim Iqbal broke a finger in the tournament's opening match and was ruled out, and Shakib Al Hasan could not play the final because of a finger injury. The top order in Dubai was rebuilt, and the middle order was, on paper, untested. The innings had to stand on Liton Das and Soumya Sarkar.

In Asia Cup history, Bangladesh have reached three finals — 2026 in Mirpur, losing to Pakistan by 2 runs; 2026 in Mirpur, losing the T20 final to India by 8 wickets; and 2026 in Dubai, losing to India by 3 wickets. Three finals, three defeats. The matches differ, but one thing repeats: each time, Bangladesh reached the final and exposed the most fragile part of their own innings.

In 2026, while covering football at Bangabandhu Stadium, I developed a habit. Sitting behind the goal, I wrote twelve-line bursts into my phone — that day the phone became a notebook, and the crowd became a haibun, where image and sound are bound together. That habit taught me that a match's real story is not on the scorecard; it lives in the gap between two overs. In the Dubai final, that gap was overs 30 to 42.

Look at the numbers coldly. Bangladesh made 222 in 48.3 overs, bowled out with 43 balls unused. At one stage the board read 120/1. Liton was on the road to a century. In the first 25 overs Bangladesh were scoring a little above five an over, having lost only one wicket — exactly the position from which a side dreams of 300.

What followed was no accident; it was a structural outcome. From over 26 to over 42 — seventeen overs — Bangladesh scored relatively little and lost wickets in a cluster. The real crack opened between overs 30 and 40, where the side began shedding runs out of fear of losing wickets; the death-overs bowling was only the consequence. The anchor survived, but nobody around him held a strike rate. 120/1 became 222; the last nine wickets fell for just 102 runs.

Now watch India's chase. Chasing 223, India did not lean on one extraordinary innings; they did the opposite — small partnerships, patience through the middle, calculated risk in the last five overs. Rohit Sharma, Dinesh Karthik, Kedar Jadhav — none made a huge score, yet 223 arrived inside 50 overs with only 7 wickets down. India did not win a high-scoring match; they won a low-scoring match of patience, precisely where Bangladesh were weakest.

Here is a counter-intuitive truth: Liton's 121 did not save Bangladesh; it bought Bangladesh time to hide its weakness. When an anchor holds strike, a team begins to believe there is no problem. But the hole deep in the batting order keeps accumulating. In the years after that final, the same hole returned again and again — fear in the middle overs, no finisher at the death, and the risk of building an entire innings around one man.

The bowling tells the same story. Bangladesh's pacers built pressure in the last ten overs, but holding that pressure required another 30 to 40 runs on the board. In a modern ODI, 222 is not enough to defend, because India had all 50 overs and wickets in hand. Mashrafe split his overs, Mustafizur Rahman bowled at the death — but chasing 223, India were never forced into real risk.

In Kazan I learned that a time-lapse is just a heartbeat refusing to slow. In Dubai it ran the other way — the whole innings was a stalled heartbeat, the side slipping a little further every over. The trapdoor opened in the 43rd over and the match fell through it, but the trapdoor had been built long before, around over 30.

In 2026, sitting alone among 81,365 empty seats at Signal Iduna Park in Dortmund, I learned that you must also hear what a stadium withholds. In Mirpur's empty stands that lesson has been useful again and again. When a side stalls in the middle overs, the crowd suddenly goes quiet — and in that quiet you hear a batter afraid of his own strike rate. In the Dubai final that silence was there, in the headphones and in the rhythm of the scoreboard.

Collective memory says Bangladesh lost the final in the last over, to a small bowling error, to fielding nerves. That explanation is comfortable, because it blames a single moment rather than a structure. In 2026 at Wembley I watched Bukayo Saka's missed penalty from behind the goal — one ball, one step, where a whole nation's grief settles. Some want to remember the Dubai final the same way, as a single penalty wound.

But in cricket, wounds are rarely made by one ball; they are made over thirty overs. The Dubai wound accumulated between overs 30 and 42 — the cautious refusal to push the run rate, the weakness in rotating strike through the middle, and the mismatch between the set batter and his partners. A side that stops at 222 from 120/1 does not have a problem in the last over; it has a problem in over 35. That never shows up in a match report; you have to read session-by-session scoring patterns.

The 2026 Mirpur final is the mirror image. That day Bangladesh reached the final over and lost by two runs; the weakness was cold calculation in the final ball. In Dubai the opposite happened — the last over arrived much later, but the match was already gone. The two finals show two different diseases: one of a miscalculated final moment, one of a miscalculated whole innings.

Since 2026, readers have written to me, each sending their own memory of 'one ball'. But I keep noticing one thing: many do not remember the scoreboard at over 30. Memory always enlarges the ending and forgets the middle — even though a match's fate is written in the middle.

The Dubai night of 2026 is a lesson Bangladesh has not fully read. In the next tournament cycle, the real question will be: breaking away from the anchor template, who is the batter who can strike above 100 from overs 35 to 45? And who is the bowler who can stop runs in the last five overs? The story of bowling failure is the least relevant here. This is the story of a team learning to know its own innings — and that innings has remained unfinished. Dubai's lights went out long ago; the question remains on the scoreboard, beside 222, burning like a small star.