144/6: The Moment the Chennai Test Actually Began

My notebook's page from 19 September 2026 is still loose. The paper curled with dried sweat, and there's a red-soil smudge in one corner — I had pulled out the notebook before taking off my shoes after returning from the stands.

At the top I had written: "Chennai. 32 degrees. Humidity close to eighty. Red soil — it sticks to your fingers, and when you wipe it off it turns to powder. The smell sits somewhere between a new tennis ball and hot coal."

Beneath it I had written a time, then crossed it out with a pen. 3:12. Afternoon.

At that moment India were 144 for 6.

I had been at the MA Chidambaram Stadium since morning. Hasan Mahmud has a habit of drawing his arm across his chest just before releasing — like someone adjusting a shirt button. I watched it in the first over of the day and noted: "He doesn't pitch it at the stumps; he pitches it four or five inches to the right of the stump line, but he forces the batsman to play."

Bangladesh won the toss. Najmul Hossain Shanto called correctly and chose to bat. It was not a wrong decision — on Chennai's red soil the seam moved in the first two sessions, the ball came in at the stumps, and in humid September Chennai the fielders' gloves went damp from the inside. Bangladesh were bowled out for 149 in the first innings. Jasprit Bumrah took four wickets alone.

Then India batted, and at 144 they had lost six.

I took out my phone and photographed the scoreboard. History says Bangladesh have never won a Test against India. They lost by 208 runs in Hyderabad in 2026, by an innings and 130 in Indore in 2026, by an innings and 46 in Kolkata in 2026.

This is where my request begins.

If you were sitting in front of the television that evening, saw 144/6 and thought about changing the channel — I have one thing to say. Sit down. Take a sip of tea. Wait.

I am waiting for you to finish tying your laces.

Because cricket has minutes we habitually label "the end." The 82nd minute is not late. The 47th over is not an epilogue. That Chennai evening was not the match's conclusion — it was the match's birth. And we spend a large part of our lives mislabelling that birth as a "rescue."

To understand how that evening was built, remember one thing. Bangladesh arrived on this tour having beaten Pakistan 2-0 in Rawalpindi in August–September 2026. It was Bangladesh's first series win against Pakistan on Pakistani soil in any format. Chasing 185 in the second Test to win by six wickets is not merely a scoreline; it is a statement of mindset.

So Bangladesh did not arrive in Chennai as mere guests. They arrived as a team with the taste of winning still on their hands.

And India? India walked into that Test playing their first Test under head coach Gautam Gambhir. Before the series, India's ODI side had lost 2-0 to Sri Lanka in Colombo — their first series defeat there since 2026. That white-ball shock does not translate directly into the Test side, but in the early days of Gambhir's Test tenure there was an unease in the air.

One more fact few in the stands knew that day: for Rishabh Pant this was his first Test since December 2026.

So the picture was this — one side freshly writing history, the other with a new coach, a returning keeper-batsman, and a red-soil pitch.

Chennai's red soil carries a widespread misunderstanding. People assume red soil means seam, means grass, means batting in the first session is suicide. Half true. The real character of red soil is that for the first thirty to forty overs the ball bounces and seams a little, and then, suddenly, the pitch dies.

That is exactly where Bangladesh's first major mistake hid.

After being bowled out for 149, Bangladesh took the field with two seamers and two spinners. In the first hour Hasan Mahmud produced first-class new-ball bowling. He held the ball towards the stumps but not full, just behind normal length. As a result India's openers were forced to leave a ball almost every over, and not a single easy run came from it.

I wrote to a friend in Chennai at the time: "Today the ball is going with the straight seam against the right-hand-left-hand pair, not the scrambled seam." He replied: "Then who is going to fool the batsman with reverse swing?"

It was the right question.

India's 144/6 was not a mere collapse. Each of those six wickets had a technical cause — in two cases the ball straightened off the pitch and took the edge, in two cases it kept low, in one the batsman stepped out of his crease, and in one it was a catch at slip. In other words, the collapse was the harvest of ball movement, not of batsmen's carelessness.

This is where I want to pause.

Because we read that 144/6 as "Bangladesh's golden opportunity." But it was something larger: India's top order had still not built a stable solution against seam movement on that surface — and that gap got sealed inside 144/6, where history will never see it.

What happened next did not happen in twenty minutes. It happened across 199 runs.

Ravichandran Ashwin and Ravindra Jadeja — what each did is simple to see in the numbers, but clearer still at the ground. Ashwin attacked. He had measured the spinners' lengths, because it was off that length that he could go back for boundaries. Jadeja did the opposite — he left balls, rotated strike, kept Ashwin on strike.

The trick of the partnership is this: one took the risk and scored, the other absorbed the risk.

Ashwin made 113, with eleven fours and two sixes. Jadeja made 86. Together they added 199. India reached 376.

And Hasan Mahmud took 5 for 83.

Read that sentence again. He is the first Bangladesh fast bowler to take a five-wicket haul on Indian soil. Bangladesh's fast bowlers have taken so few five-wicket hauls in Test cricket that the list fits in two or three lines on a single page. On my desk there is a file — the "Rising Star file" — where I arrange two dozen young cricketers by age. Hasan Mahmud's name has been in it since 2026. That Chennai evening did not strike it out; it forced me to put a star beside it.

But these two events — Ashwin's 113 and Hasan Mahmud's 5/83 — happened in the same Test, and in our memory their weights are unequal. That is the real story.

I have been writing cricket for years, and I have seen one thing repeatedly: Test collapses do not survive memory; rescues do. In Chennai, when Bangladesh's fielders stood on the ground for 76 overs after those six wickets, the sweat of those 76 overs never reaches the scorebook. But Ashwin's cover drive will return in every season-ending montage.

Here I want to say something that may make some people uncomfortable.

Twentieth-century cricket memory was innings-centred. Twenty-first-century cricket memory has become partnership-centred — and through that shift, the hardest task in Test cricket, knocking over six wickets with the new ball, has been almost erased from memory. We will remember the 199. We will not remember the 6.

Yet inside 144/6 lay the real signal. The problem India's top order exposed in Chennai's first session returned months later on Australia's quick and bouncy pitches. In Chennai it was buried because two lower-order men covered for it.

Now the other side. Why could Bangladesh not finish it?

First, ball age. In the first hour Hasan and Taskin could move the seam; after thirty overs that capacity fades. In a post-match conversation I asked a senior Bangladesh bowler: "Why did the line shift a little between the thirtieth and fortieth overs?" He answered: "When red soil dies, pitching it on the seam line no longer makes it top-edge. Then you have to make the batsman play."

The answer is honest. But it leaves a question: while Ashwin and Jadeja were adding 199, a Bangladesh spinner was changing strike almost every over, yet no line-and-length consistency was built.

Second, the link between bounce and length. Bangladesh had the option of a third seamer beyond their two new-ball bowlers, and not taking it forced Shanto to keep returning to a spinner through the middle overs, denying him the variation of length Ashwin needed to face.

The third reason is psychological. 144/6 means six wickets — but slip, gully and short leg still had seven or eight fielders standing. Taking wickets required patience, and patience in cricket is very often an unglamorous job.

There is one more point I personally consider vital. The story of Bangladesh's fast bowling over the last five years has largely been about pace, physical build, and the eye of franchise-league auctions. In such a structure a young seamer learns how to show 140-plus; he does not learn how to hold a fourth-stump line for eight overs and wait. Hasan Mahmud's Chennai spell is an exception — a victory of craft, not of athleticism.

And exceptions become the most memorable things of all, if we give them time.

In the second innings of the Chennai Test, Bangladesh made 234. Batting again, India declared on 287 for 4; Rishabh Pant made 109 there, and Shubman Gill was unbeaten on 119. India won by 280 runs. Ashwin was Player of the Match.

The scorecard is tidy, clean. And it is precisely in that tidiness that 144/6 disappears.

Now let me argue the other way.

The conventional reading is: Ashwin's 113 saved the match, Bangladesh let a golden chance slip, India won by 280 runs. But there is an uncomfortable factual question here. On a Chennai wicket, a Bangladesh fast bowler took five wickets, and an Indian lower-order batsman made 113. Between those two, which is the rarer event in history?

The answer favours Bangladesh.

A hundred by an Indian spin all-rounder at home is not a rarity; it is an expectation. Ravichandran Ashwin grew up on Chennai soil, scored centuries on it against England, and saved a series there with the bat. But a Bangladesh pace bowler, on Indian soil, on red soil, having lost the toss and fielded, taking 5 for 83 — that is an event standing at the edge of history.

So my contrarian claim is this: the most historically significant thing that happened at Chepauk in September 2026 was not Ashwin's 113; it was Hasan Mahmud's 5/83 — and the fact that it became a footnote rather than a reference point proves where cricket's collective memory spends its electricity and where it leaves things in the dark.

Let me add a second uncomfortable point. We call that Test "dramatic." But India's rescue from 144/6 was not reassuring news for their top order; it was a warning for the future, and everyone inside the dressing room knew it. If in a Test you are 144 for 6 at home, on your own pitch, in front of your own crowd, that is not an accident — that is a gap. Months later, on Australia's quick pitches, that gap reappeared. Nobody links it to Ashwin's 113, because gratitude and analysis do not run together.

And one more thing we forget easily — in 2026, the silence of stadiums was the loudest player on the field. In the pandemic year I heard a single bat-on-ball thud echo around an entire ground. That Chennai evening was the exact opposite: the roar of 52,000 people, then a one-second freeze at the moment of a six, then the roar again. But at the end of that day I wrote in my notebook: "The loudest sound was actually in the second before Bangladesh's slip catch." In the second before that catch went down, every sound in the stadium seemed to hang on a wire. Television cameras do not catch that; only someone sitting close by feels it.

I know some readers in Bangladesh will say this is a story of regret. And some in Delhi or Chennai will say it is a story of Indian glory.

Both are wrong.

Because our two cities' memories picked two different things out of the same match. In Dhaka the memory is 149 and 234 — a repeat of a familiar ache. In Chennai the memory is Ashwin's cover drive — a repeat of a familiar joy. In neither memory does 144/6 exist. Yet 144/6 was the only moment when India and Bangladesh stood at equal weight — neither bigger, neither smaller.

My father has an old radio, on which in the 1980s he used to listen to Tests from Kolkata while sitting in Dhaka, because on this side of the border there was no television. What I watched from the stands in Chennai sits three thousand kilometres and forty years away from that, but the experience is identical — nobody tells the real story of a match, because the real story never reaches the scoreboard.

So what is the lesson I take from that Chennai evening?

There are two kinds of days in cricket. On one kind, the winner builds a memory and the loser forgets. On the second kind, a few people pick up something small and keep it — a delivery, a grip, a catch or a cover drive — and years later that becomes archaeology.

When someone from your generation asks in 2040, "How many runs did Bangladesh score on Indian soil in 2026?" someone may tell them: 149 and 234, India won by 280 runs. But if you finished tying your laces and sat in front of the television that day, you can give them one more number, and that will be the real number.

One hundred and forty-four. Six.

The score belonged to India. The opportunity belonged to Bangladesh. The moment belonged to cricket.

Next time someone tells you a Test match is over — ask them, in which over?

Because I have watched for years and learned this: a Test does not end with the declaration. A Test ends the day the scoreboard updates for the last time — while the real ending happened three days earlier, on red soil, on a soft length, off a settled hand.