Two Wins in Rawalpindi, One Buried Crack

Two Wins in Rawalpindi, One Buried Crack

August 2026. The second day of the first Test in Rawalpindi. It was half past midnight in Brisbane, the tea had gone cold an hour earlier, and the scoreboard on my screen read Bangladesh 26 for 6.

I did not close the laptop. That number has its own row in my spreadsheet, and it has had one for years. Mushfiqur Rahim and Mehidy Hasan Miraz were at the crease. What followed over the next few hours became one of the bravest passages of either man's career: a 196-run seventh-wicket stand. Mushfiqur 191, Mehidy 77. Bangladesh 565.

Pakistan folded for 146. Bangladesh knocked off 30 and won the first Test by 10 wickets. In the second Test, Litton Das made 138 and Bangladesh chased down the target with six wickets in hand to take the series 2-0. It was Bangladesh's first Test series win on Pakistani soil.

It is a lovely story. It is also half a story. The top order did not win those two Tests. The seventh and eighth men did, aided by a Pakistani batting collapse. The crack at the top of the order was covered over, not repaired.

Context: Two decades of away numbers

Bangladesh played their first Test in Dhaka in November 2026, against India. Two decades on, the list of away Test wins still fits on your fingers: St Vincent and then Grenada in July 2026; Harare in April 2026; the P Sara Oval in Colombo in March 2026; Kingston in July 2026; Harare again in July 2026; Mount Maunganui in January 2026; and two in Rawalpindi in August and September 2026.

The Rawalpindi series is the biggest of them, because the opponent was Pakistan, the conditions were theirs, and Bangladesh won both Tests chasing. The official ICC scorecard records that Pakistan's second innings in the first Test lasted only 146 runs.

Nahid Rana's pace stood out — regularly above 145 kph, a genuinely new picture for Bangladesh in Test cricket. Hasan Mahmud found seam movement; Taskin Ahmed brought red-ball experience. This is where most observers stop, and announce that Bangladesh's pace revolution has arrived.

I did not stop there. In the very next Test of the same series, Bangladesh's first innings was only 262, rescued by Litton Das's 138 — again a middle-order batter. Across two first innings in two Tests, the platform came from numbers five to seven, not numbers one to three.

Core: I went looking for Bangladesh's Test data

Twenty-odd years of watching this side has taught me one thing: Bangladesh's away Test results are decided by two variables — the first-innings score, and who makes it. When both are healthy, Bangladesh either win or save the match. When one fails, the game turns inside three days.

Laying out the last decade of away Tests in my spreadsheet makes the pattern plain. Almost every away Test in which Bangladesh passed 300 in the first innings ended in a win or a draw. Mount Maunganui 2026: 458, won. Rawalpindi 2026, first Test: 565, won. Where the first innings collapsed below 230, an innings defeat has become close to routine.

The second Rawalpindi Test is the exception to that rule, and the exception is the real lesson. A first innings of 262 should normally mean defeat. Bangladesh won because Pakistan were bowled out for 172 in their second innings. The win came from the opponent's collapse, not from Bangladesh's control. That distinction never shows up in the result column. It shows up in the next series.

I have watched Bangladesh for 23 years, watched them get bounced out by short bowling, watched them grope at swing and seam. A fragile top order is not a new discovery. What is new is the widening gap between the middle order and the top order in the 2026 numbers — the gap has grown, not shrunk.

Shadman Islam, Zakir Hasan, Najmul Hossain Shanto and Mominul Haque, taken together, average far below what comparable batters for the top eight Test nations manage away from home. The home numbers look kinder, but that kindness comes largely from slow Mirpur surfaces and low bounce, not from a better method.

There is a football lesson here, since I track both codes. Possession percentage is the most deceptive statistic in football — sixty per cent of the ball and forty-eight sideways passes produce fewer goals than four passes and a shot. In Test cricket, balls faced is the same kind of decoy. Surviving four deliveries and dead-batting a fifth is not concentration; it is delayed decision-making. Useless running to third man looks beautiful on a tracking chart and adds nothing to an innings.

This is precisely where Bangladesh's top order frays. The feet barely move before the ball is released; the shot is chosen after it. Dot balls pile up, pressure builds, and one loose stroke ends it.

The louder the numbers talked, the louder the old eye test laughed. The honest position is to listen to both at once, and let neither drown the other out.

The home spin-fortress story

Some cricket stories do not survive on their own; they need patrons. The spin-fortress tale is patronised by a handful of memorable wins and a handful of quickly forgotten defeats.

In December 2026, Bangladesh beat New Zealand by 150 runs in Sylhet — their first home Test win over New Zealand. That was a genuine achievement, and home advantage did the work. In the very next Test, at Mirpur, New Zealand won.

Then came October 2026. South Africa, at home. Bangladesh lost the first Test by seven wickets. In Chattogram, South Africa won by an innings and 273 runs. According to ESPNcricinfo's match report, that remains Bangladesh's heaviest defeat in Test history. Home soil, home crowd, home conditions — and still.

Why do those two facts sit side by side? Because the fortress idea rests on the character of the pitch, not on the batting order. When Bangladesh win, the reason is usually a first innings of 300-plus. And that score most often comes from numbers seven and eight. If the top order falls for 30 or 50, the best spin bowling in the world turns a 20-wicket equation into a 15-wicket equation.

A second doubt follows. If Mirpur stays slow and responsive to counter-spin, the top-order weakness will be masked, Bangladesh will win, and the win will be explained through spin rather than batting. That is tactical comfort, not structural progress. And comfort has one reliable enemy: time.

I wanted Bangladesh to prove me wrong

Watching Nahid Rana, I pay more attention than usual. In Rawalpindi in 2026, his pace and front-foot control suggested a component Bangladesh had never had. Hasan Mahmud can use helpful conditions; Taskin Ahmed has red-ball experience. At the 2026 Champions Trophy, the group stage offered early hints of the same.

So my own argument deserves an honest objection: perhaps I am fixated on an old wound and talking like it is the 1990s. Perhaps this pace attack is dragging innings into a place where 260 is enough.

The objection carries weight. Most of Bangladesh's away Tests come in SENA conditions — South Africa, England, New Zealand, Australia. There is no harder assignment in the sport. Every side has suffered there. Why should Bangladesh be exempt?

But the counter-witness is stubborn. The innings-and-273-runs defeat in Chattogram in October 2026 happened at home, in home conditions, on a surface that helped spin. If conditions were the only cause, it would not have happened there. What was visible instead — footwork, the timing of the shot decision, the structure of the order — looked exactly like the away problem. The issue is structural, not geographical.

There is one more thing still unrecognised. After Rawalpindi, this side began to show a new capacity: it has learned to build an innings slowly, from inside a big total. The route from 26 for 6 to 565 is the proof. But that capacity is being produced at six and seven, not at one and three. A team that absorbs 26 for 6 and reaches 565 deserves praise. A team that reaches 26 for 6 deserves the criticism.

A counterfactual keeps circling. If Mehidy's innings and Mushfiqur's 191 had not existed in Rawalpindi, what would the pace-revolution story sound like today? Probably like a hard-fought series split, with the top-order question returning louder.

I would like to be wrong. I would like Bangladesh's Test batting to take another leap and leave my spreadsheet looking stale. But my doubt is structural, not personal.

Takeaway: what to watch

My arithmetic can be tested in the next series, and the test is simple. If Bangladesh's numbers one to four collectively average below 25 in the first innings of an away Test, no amount of Nahid Rana pace will win that match. Pace is part of a match. A first-innings foundation is a different part.

At home, watch the language of the pitch. If Mirpur stays slow and counter-spin friendly, the top-order weakness will hide and Bangladesh will win — and the win will be credited to spin, not batting. That is comfort, not progress.

I am willing to throw out the batting data. But first I want to see the top order pass 350 three times — not at home, but away. Until then, that 26 for 6 in Rawalpindi stays in the top row of my spreadsheet, and I am not closing the laptop.