A 326 Chase in Lahore, and the 110 All Out in the Same Series

48.3 overs. Three wickets in hand. Nine balls left. At the crease, a man picked primarily to bowl. Shaheen Shah Afridi cleared the rope, the score reached 331, and the Lahore ground erupted the way a ground should erupt after 656 runs in a final. That frame will travel for weeks — a fast bowler's bat, a record chase, a home final.

I have read scorecards for close to three decades, and I will not pretend that the six was the interesting part. The interesting part was that a team pursuing 326 was still alive at the 48th over. The required rate never reached the point where an innings breaks; it only approached the point where fear begins. I don't start with the thesis; I start with the weird detail that won't leave. Here it is a bowler's bat — and even that arrived with nine balls and a handful of runs still owed.

Which patch this match was played on

A tri-nation final in Lahore. Sri Lanka batted first and made 325/8, built around Kamindu Mendis's 131. Pakistan reached 331/7 with three wickets and nine balls in hand. The aggregate of 656 is being described as the highest combined total in a tri-nation series or tournament final.

The 326 chase equals the one India completed against England in the 2026 tri-nation final, and it is being described as the highest successful chase in an ODI tournament knockout. The win is Pakistan's first multi-nation ODI title since the 2026 Champions Trophy — roughly a nine-year gap.

One fact needs recording here. Earlier in the same series, against the same opponent, this same batting line-up was bowled out for 110. I left the desk in 2026 and found the story already mid-sentence. This series arrived half-written too: one team, one rival, and two scores separated by 221 runs. The coverage chose one of them, and it chose the one that was easier to share.

Score box

• Sri Lanka 325/8; Pakistan 331/7 (approx. 48.3 overs)
• Kamindu Mendis 131 — Sri Lanka's third-highest ODI final score, behind Jayasuriya's 189 and Atapattu's 132*
• Second-highest individual score in an ODI final against Pakistan; Brian Lara's 153 (2026) tops that list
• 331 is Pakistan's second-highest ODI knockout score; 338/4 against India in the 2026 Champions Trophy final is first
• Combined aggregate 656 — a tri-nation final record

The core: a chase runs on a timer, not on runs

In esports, when a team plays around an objective — Baron, Dragon, Roshan — the real resource is not gold. It is the timer. Timer gone, resource gone, whatever the scoreboard says. In an ODI chase, that timer is the required run rate, and its most important property is that it does not rise linearly: its value changes with every wicket.

On this evidence, Pakistan never won the timer and never lost it either. Three wickets still standing at the 48th over means capital was intact, and the last nine balls forced that capital to be spent at six or seven an over. The same side that can be bowled out for 110 sat on three wickets for 48 overs. Both facts belong to the same team. That is the knot in this match, and it is why I call this structure, not transformation.

Fakhar Zaman's actual patch

Fakhar Zaman offers the cleanest signal here. Four thousand ODI runs in 96 innings is the second-fastest by a Pakistan batter. The milestone matters less than its conditions: four ODI centuries while chasing 300-plus. That is a Pakistan record; Babar Azam and Younis Khan sit behind him on three each. The number describes a mode — Fakhar is most dangerous when the board is already under pressure and the task is pursuit rather than construction.

Three ODI tournament finals, two centuries. Only the second Pakistan batter after Saeed Anwar to do that. I stop here, because this is where the easiest error begins. Three finals are not a trend; they are three events, played on different pitches, against different attacks, under different targets. Calling Fakhar a final specialist is a conclusion resting on a sample that will not carry it. What carries weight is the 300-plus chase record, because the conditions repeat: quick start, big target, an attack that must be attacked.

Babar's counter-number

Babar Azam reached 4,000 ODI runs in 82 innings. If Fakhar is 'second-fastest' at 96, then Babar is Pakistan's fastest — a conclusion that falls straight out of the numbers, and one that has been oddly under-written. He has three centuries in 300-plus chases, one behind Fakhar. So this is not one batter's team; it is a side carrying two different batting modes at once.

A reporting fault needs logging too. One line calls this Shaheen Shah Afridi's team; another calls it Babar and Shaheen's side. Captaincy is a fact, not an editorial habit. Until the official XI and captain are confirmed, the contradiction sits in the copy. The Jakarta credential was paper; the six-week queue was the real interview. A scorecard is paper too; verification is the interview.

Arafat Minhas: the most interesting and the most dangerous number

Arafat Minhas has two fifty-plus scores and two five-wicket hauls in his first eight ODIs — only the second cricketer to do it, after JJ Smit in his first ten. That is a genuine signal, and a useful one for Pakistan's balance: a player who can move the scoreboard with both bat and ball.

Eight matches are not a career. The sample carries no batting position, no bowling style, no opposition quality, no home-away split. 'Next big all-rounder' language starts here and goes wrong here. Wait for twenty or thirty ODIs before projecting anything.

Sri Lanka's side: a 131 that lost

Kamindu Mendis's 131 is Sri Lanka's third-highest ODI final score, behind Jayasuriya's 189 and Atapattu's 132*. Against Pakistan in any ODI final, only Brian Lara's 153 in 2026 stands above it. Read those two lines and it sounds decisive. It was not. On a Lahore surface, 325/8 is not automatically a winning total; the question is how many of those runs arrived in the last ten overs. That slice is not in the available scorecard detail, and until it is, 131 is better called match-defining than match-winning.

The contrarian case: what this record does not prove

The strongest objection first. Someone will argue that chasing 326 with three wickets and nine balls left proves a new maturity in Pakistan's batting. I accept the objection and return to the same dataset it came from. Earlier in the same series, against the same opponent, this team was dismissed for 110. Both numbers come from the same conditions and the same sample, and they cancel each other. The conclusion is volatility, not maturity — and volatility cuts both ways, which is exactly why the same side can produce the week's biggest chase.

Second, the bowling. The 331 was needed because Pakistan conceded 325/8. No bowler-level figures are available, so I will not claim the attack is weak — only that this part of the story vanishes from a record-chase narrative because it does not face the win.

Third, and least comfortable: every record anchoring this report has no named source. Until an official ICC or ESPNcricinfo scorecard confirms them, these claims are verifiable, not verified. One counterfactual, clearly labelled: had the same 326 target arrived on an away tour against a top-six attack, where the 48.3-over timer would have broken is not something the data can currently answer.

Forward

Pakistan's next away ODI series will say more than this final did. If the top order shows the same 48-over patience across five to ten matches, Lahore was a beginning. If the 110 pattern returns, 331 was a good day. For now: 48.3 overs, three wickets, a bowler's six. Freeze that frame. I will not call it a revival. I will call it a patch that won one match, whose real effect shows up next series.