The Survival Lesson: From Rawalpindi to Kanpur, the Wrong Thing Bangladesh's Test Batting Learned

First week of September, Rawalpindi. The match ended before evening. I saw Shanto in the dressing-room corridor — helmet in hand, wearing that particular exhaustion that only follows a win. My notebook page read: "The stadium is nearly empty, yet there is no silence." Seven or eight Bangladeshi expatriates stood outside with green-and-red flags, some of them crying — and around them, near-total quiet. Six weeks later, at Green Park in Kanpur, I heard the same dressing-room silence again. This time it was not belief. It was surrender.

In the bubble I learned that silence has a pulse if you listen long enough. Rawalpindi's pulse was quick and warm. Kanpur's was slow, cold, almost still.

Context: the two weeks that reshaped Bangladesh's Test identity

On 25 August 2026 at Rawalpindi Cricket Stadium, Bangladesh replied to Pakistan's 448/6 declared with 565 — Mushfiqur Rahim 191, Shadman Islam 93, Mehidy Hasan Miraz 77. Pakistan were then bowled out for 146 in their second innings, and Bangladesh knocked off 30 for a ten-wicket win. It was their first-ever Test victory over Pakistan.

Then on 3 September, at the same ground: Pakistan 274 and 172, Bangladesh 262 and 185/4 — a six-wicket win, the series 2-0. In the second Test's first innings Bangladesh had been 26/6. Litton Das's 138 and Mehidy Hasan Miraz's 78 lifted them to 262. That 165-run seventh-wicket stand did not merely save the match; it reversed the whole series.

Then came the India tour. On 19 September at the M. A. Chidambaram Stadium in Chennai, Bangladesh made 149 and 234; India made 376 and 287/4 declared. India won by 280 runs. Ravichandran Ashwin scored 113 and took 6/88 — Player of the Match. Across two innings, Bangladesh's middle order survived roughly three hundred balls against the Ashwin-Jadeja pairing but found runs only in scattered boundaries.

Then 27 September at Green Park, Kanpur. In a rain-truncated match Bangladesh made 233 and 146; India made 285/9 declared and chased 95 for the loss of three wickets. India took the series 2-0.

Two countries, two outcomes. The real story, though, is not on the scorecard. It is in the gaps of the scorecard. The pattern I have been noting from the Daily Star desk since 2026 was exposed most clearly by this series.

Core: when survival becomes the strategy

The lesson Bangladesh's Test batting took from Rawalpindi was "survive first." But the mechanism by which they actually won was "counter-attack under pressure." The distance between those two is the whole explanation of the India tour.

Think of the second Rawalpindi Test. 26/6 is not a survival position; it is nearly the end. What Litton and Mehidy did there was unvarnished counter-attack — not the patience of defensive batting, but deliberate, conscious strokes against the length. Litton's 138 mixed cover drives, square cuts and sweeps; Mehidy batted straight but never let the run rate sink below two. That 165-run stand pulled the team back into the match, and then into the series.

In Chennai, Bangladesh did the opposite. Their first innings of 149 says the batters did not last long. But their second innings of 234 took nearly eighty overs. They survived without advancing. The gap between patience and progress is Bangladesh's real fracture.

Going back through the ball-by-ball sheets, one thing is clear: Bangladesh's top order in Chennai and Kanpur both negotiated the first ten to fifteen overs relatively safely. The collapse came afterwards, when the scoreboard was pinned down but the runs did not come. The team froze in an uncomfortable middle state: neither attacking nor moving the scoreboard. Fielders crowded the bat, spinners found traction, and every dot ball made the next one heavier.

Here is the genuinely counter-intuitive point: Bangladesh do not lose to India's spin or bounce. They lose to the inertia they create themselves. In Kanpur, India declared at 285/9 — that declaration was not just a scoreboard decision but a statement. "We will not burn time; we will manufacture results" — that mindset held a mirror up to Bangladesh, and Bangladesh did not recognise itself in it.

This pattern is not Bangladesh's alone. Across Asian Test cricket there is a common tendency: subcontinental sides treat patience as a virtue and file the run rate away in a separate box. Sri Lanka escaped the trap because their top order learned to own the tempo of an innings; Pakistan keep falling into it. In 2026 Bangladesh stood exactly in the middle — they escaped at Rawalpindi, then walked back in at Kanpur.

Contrarian: the misreading from outside

The most repeated analysis after the series was: "Bangladesh's batters cannot handle pace and bounce." From outside it sounds reasonable. It also buries the real picture.

At Rawalpindi, the same batters put up 565 against Pakistan's pace attack. If a defeat to Bumrah, Siraj, Jadeja and Ashwin were purely a matter of technique, technique does not change that much in six weeks. It does not.

What changes is the match plan and the mental frame. In Rawalpindi, Bangladesh played reactive but purposeful cricket — a worthy answer to whatever ball arrived. In India they played inside a different frame: survive first, score later. And the "later" never came.

The second popular misreading — "there is no leadership in Bangladesh's batting order" — is also a half-truth. The real problem is role clarity: nobody in Bangladesh's top order accepted "holding the scoring rate" as their own responsibility. Everyone waited, afraid that playing a shot meant getting out. A team that waits never sets the tempo of an innings; it accepts the tempo.

And one more thing that rarely reaches the press box. In that Kanpur match, when the rain came, I saw a few support staff and two security guards standing quietly on the dressing-room balcony. My notebook read: "This quiet is not defeat. It is confusion." The team did not know what it wanted — a draw, or a result? The rain here is not an opponent but a mirror: to a side that does not know its own purpose, time means only fatigue.

Takeaway: the signal ahead

In October 2026 the Bangladesh Cricket Board's leadership changed, and Phil Simmons took charge as head coach. But no coach alone can shift a team's mental set. That takes one decision: Bangladesh's Test batting must stop treating survival as success.

I kept the notebook open until the fans wrote themselves into the story — a man outside Kanpur, who has watched Bangladesh cricket for three decades, told me: "We can lose. But we cannot lose like that, without a trace of effort." Two time zones taught me that one heartbeat can cross every border — but holding a heartbeat requires cardiac output, not just patience.

The question now sits with the next home series. Will Bangladesh learn that surviving a Test and advancing through one are not the same thing? Or will they return to the old consolation — "we played well, the runs just did not come"?