Rawalpindi's 305: Where Salman's Century Covered Three Unfinished Innings

First Beat: The 29 Balls After the 45th Over

Four of us were at a tea table in Rajshahi, doing the arithmetic out loud. 279 for 6, five overs left, one set batter, and Rawalpindi's short boundaries. Someone said 340. Someone said 355. The next 29 balls produced 26 runs and four wickets. The sound of a tea glass being set down was the clearest commentary of the evening. The first beat was a tea glass clinking in Rajshahi; what settled on the scoreboard afterwards was 305.

Years of watching this game have taught me one thing: death-over collapses do not arrive suddenly. They are built in the 45th over, and they are built in the 25th. If an all-out 305 is simply filed away as "a fighting total", the useful question disappears: could this side have reached 335 from 279 for 6, and if not, was the fault the batters' or the structure's?

Reading 305 at Rawalpindi

Opening fixture of a tri-nation ODI series, Pakistan hosting at Rawalpindi Cricket Stadium. Pakistan were asked to bat. The innings ended at 305 all out in 49.5 overs — effectively a full-length ODI innings, one ball short of fifty overs.

Rawalpindi's character, from long observation rather than this report, is batter-friendly: short boundaries, true pace and bounce. There is no pitch report in the source material, so that is venue history, not this day's evidence. Even with that caveat, 305 at Rawalpindi is par-or-below, not a fortress total.

Equally important is what the source does not contain: no second-innings data, no result, no series context, no ICC rankings, no identity for the third tri-series participant. No indication of day or night cricket, so no dew assessment; no rain, so no Duckworth-Lewis angle. I will not speculate on any of it.

The Innings Map

32 for 2 at 5.5 overs. 106 for 3 at 19.4 — 74 runs in 83 balls, a 5.35 run rate. Around 20.4 overs, 110 for 4, a second cluster of wickets. Then 215 for 5 at 37.2 overs — roughly 105 runs in 100 balls at 6.30. A sixth-wicket stand added 64 in 46 balls at 8.35, taking the score to 279 for 6 at 45 overs. The last 29 balls brought 26 runs and four wickets at 5.38, ending at 305 all out in 49.5.

The acceleration was correctly timed — 5.35 to 6.30 to 8.35 is textbook death-overs escalation. But the escalation rested on a single partnership, and when it broke there were 29 balls left and no set batter.

Salman's Century and Three Unfinished Innings

Salman Ali Agha's hundred is the innings' central fact. Six of the top seven reached double figures; only Salman passed fifty. Babar Azam made 45, Saad Baig 39, Hasan Nawaz 37 — three innings in the thirty-to-forty-five band, all set, none converted.

That is the classic platform-without-finisher profile. Had two of those three gone on, Pakistan would have been 340 for 4 at 45 overs, and the last five overs would never have needed a new batter.

Sri Lanka's Two Edges and a Silent Middle

Sri Lanka's bowling burned at both ends and went quiet in between. Madushanka struck in the fourth and sixth overs to produce the 32 for 2. Malinga's late cluster — Faheem, Naseem, a near hat-trick — closed the innings.

Between the 21st and 45th overs, apart from Fernando's two strikes, no bowler took a wicket. Nearly twenty-four overs, two wickets. That is the window in which Pakistan rebuilt at 6.30 and then accelerated to 8.35. The final 4.5 overs, in which Sri Lanka took four wickets at 5.38, were good bowling. The barren middle was the real problem.

The Last 29 Balls

The scorecard calls it a collapse. It reads more like a structural outcome. The innings' entire tempo depended on one partnership, which ended in the 45th over. The incoming batter inherited an 8.35 expectation, 29 balls, and no set partner — the most unforgiving position in ODI batting. The source does not name the sixth-wicket pair, so I will not assign blame. What is certain: four wickets fell for 26 runs in 29 balls.

A Data Check Worth Flagging

The analysis states Pakistan "lost their last five wickets for just 26 runs". Its own phase map contradicts that: 279 for 6 at 45 overs to 305 all out means four wickets for 26 runs. If five had fallen for 26, the slide would have begun at 279 for 5, which conflicts with the 64-run sixth-wicket stand. Four wickets means a set pair was broken and the innings stalled. Five would mean the innings disintegrated inside the last five overs. The difference matters, and the source contains an arithmetic error.

Why the Outside Reading Misses

The headline calls 305 a fighting total. Emotionally fair, arithmetically questionable. Whether 305 defends at Rawalpindi cannot be judged without the chase — but the ground's character suggests it is gettable. The first outside error is treating 305 as an achievement rather than as 20 to 35 runs left behind. The second is calling the collapse a batting failure; it was a planning failure. A side that bats at 6.30 for twenty-four middle overs without a separate death plan is one broken partnership away from exactly this. The third error sits with Sri Lanka: their last-over bowling deserves praise, but the match turned in the wicketless middle.

An empty Yellow Wall still has a pulse if you listen. So does a 305 — but only once the chase is heard, and the chase is not in the source.

What to Watch Next

Three things. Whether Sri Lanka's new-ball pair can repeat Madushanka's first spell. Whether the middle-over wicket drought recurs, because if it does, 305 will look small. And whether Pakistan change their last-five-overs plan, since repeating the same mistake twice stops being an accident. The question is simple: is 305 at Rawalpindi a fighting total, or an unfinished sentence waiting for its second innings?