Pakistan's 110 in Lahore Was Settled by Over 13.1

The first ball of the 13th over went down, and Pakistan's fifth wicket went with it: 61 for 5. A 50-over match still had 37 overs to run, five batters left in the shed, and no stand on the card that had lasted long enough to be called a partnership. The innings ended at 110 in 25.3 overs, with 147 balls unused — less than half the resource spent.

On the overnight desk, every score arrives as a small confession. This one confessed that Pakistan's middle order never took the field. Twenty-one years of reading scorecards has taught me to count the balls left over before counting the runs. The count here is 147.

It was the fifth match of a home tri-series, and Pakistan chose to bat. The source material carries no pitch report, no weather, no dew, no toss nuance and no account of Sri Lanka's chase — which means the conditions-versus-process question cannot be settled from it. What is on record is the scorecard, and the scorecard is unusually articulate.

Sri Lanka brought three different trajectories: Dilshan Madushanka's left-arm pace, Wellalage's left-arm spin, Arachchige's off-spin. That is the exact mix that exposes a top order short of time in the middle. Madushanka finished with 5 for 34 in 8.3 overs — economy 4.00, a wicket every 10.2 balls.

The history was already speaking. Against Sri Lanka at Gaddafi Stadium, Pakistan had been bowled out for 75 in 2026 (second innings, the venue's lowest) and 102 in 2026. Now 110, the lowest batting-first total at this ground. Sixteen years, several squads, one opponent, one venue.

The collapse was front-loaded, not a late slide. Three wickets fell inside the first seven overs. Fakhar Zaman made 5, Maaz Sadaqat 8, Saad Baig 5 — the top three aggregating 18 runs off 32 balls. That profile is not one batter's technical flaw; it is a collective inability to survive the new ball.

The number that matters is not 110. It is a team strike rate of 71.9. One hundred and ten off 153 balls, against a modern ODI competitive benchmark of roughly 90. Runs stalled and balls were burned. The itemised boundaries — five fours, three sixes — account for at least 38 runs, more than 34.5 per cent of the total. The rest arrived at well under four an over.

No partnership of substance existed. The fifth wicket fell at 61 and the innings ended at 110, which means no stand passed the mid-40s. In a 50-over format the team never reached its platform phase, and the lower order was exposed to full attacking fields.

Babar Azam's 29 off 33, with five fours and a strike rate of 87.9, was the top score. It was simultaneously the best and the most damning innings of the match. His rate was above the team's; he was still dismissed inside the 61-for-5 cluster, by Eshan Malinga, and the terminal slide began with his exit. A top score of 29 in a completed ODI is not one batter's failure. It is the question of why the side's finest technician was sent to defend rather than to build.

Shadab Khan is the cleanest narrative-versus-data trap in this file. A maiden ODI century against England in the previous match, then 2 off 5 against Arachchige's spin. The century was a career outlier, not a new baseline. His value is as a spin-bowling all-rounder, and asking that profile to rescue 61 for 5 is a squad-structure problem, not a Shadab problem.

Hasan Nawaz survived 31 balls for 17, a strike rate of 54.8, with 11 runs off 30 balls outside his one six. Salman Ali Agha made 9 off 14, Arafat Minhas 10 off 18 — two more sub-70 strike-rate innings compounding the same slowdown.

Shaheen Afridi's contribution reads differently: 15 off 13 at 115.4, two sixes, the team's second-most effective rate. He was also the captain of an innings that ended in 25.3 overs. The structural conflict of a fast-bowling captain sits right here: ten overs of his own, field settings and batting-order calls all run through one head. That is a medium-confidence concern, not a proven cause.

Madushanka's five-for deserves a qualified reading. Two of the five were specialist bowlers — Haris Rauf and Shaheen. An economy of 4.00 and a wicket every 10.2 balls is match-winning, but with no separate data on his new-ball spell, this is not yet evidence of a repeatable top-order-breaking skill. Left-arm pace is a scarce profile, and markets always overpay for scarce profiles.

What this data does not prove is that batting first was the wrong call. Pakistan chose to bat and the source calls the start disastrous, but the pitch behaviour, the dew and the outcome of Sri Lanka's chase are all absent. Without them nobody can say whether 110 was par, below par, or unplayable. What can be judged is the process inside the innings.

The second inversion sits in the headline. Second-lowest ODI total in Lahore sounds enormous, but it merges an all-time venue record with a batting-first record — the 75 in 2026 came in the second innings. The more diagnostic figure is 147 unused balls, and beyond that, the same collapse three times in sixteen years.

The biggest risk now is a backlash against the young batters. Maaz Sadaqat and Saad Baig walked in at three down inside seven overs; 8 and 5 in that situation is a plausible output, not a failure. Judge them on ten innings. And remember that Pakistan did not bowl in this data, so a crisis-across-all-disciplines conclusion does not follow from this file.

The last thing missing from the record is the crowd. A silent stadium is still a stadium; a silent crowd is a question — and in this report the noise was never written down at all.

The next ODI decides the reading. Bat first again and reach 280, and Lahore becomes an outlier of conditions. Sink below 200 once more, and it becomes a report card on the domestic 50-over structure.

The question is not how 110 happened. The question is why we count the 110 and not the 147 — and who benefits from that ledger.