Pakistan's 110 in Lahore: 147 Balls Left Unused, and That Is the Real Story

13.1 overs. The Gaddafi Stadium scoreboard read 61-5 and my stream in Manchester was running two seconds behind. I could not feel the pitch, the evening heat in Lahore, or that specific silence that settles over a home ground when the fifth wicket falls. What I had was the scorecard — and the scorecard carried one number no headline used: the innings ended at 25.3 overs. 147 deliveries went unused.

That bio-secure summer of 2026 comes back to me often, when I logged four thousand three hundred deliveries at Emirates Old Trafford with the stump mics open. It gave me a habit: before I read a result, I count consumption. How much resource was spent, in which phase, and by whose hands. In Lahore the answer was blunt — more than half the innings was never spent.

So my claim is stated plainly and early, so the caveats can work around it: 110 was not a pitch outcome. It was a failure of new-ball survival and middle-overs strike rotation. That distinction matters because the first accusation lands on talent and the second on selection structure, and the two have entirely different cures.

What the report does not say

The material available is a match report: match five of a tri-series, a Pakistan home fixture, Pakistan chose to bat, all out for 110 in 25.3 overs. What is absent matters as much: no pitch report, no weather, no dew, no DLS information, and — most strikingly — no outcome for Sri Lanka's chase. A match report this silent about a chase is usually telling you the chase was never a contest. That is an inference from omission, not data, and I label it as such.

The immediate consequence is that "batting first was the wrong call" does not follow from this dataset. To separate 110-par from 110-subpar from unplayable, I need both the pitch behaviour and the chase. I have neither. Drawing a conclusion from absent evidence is the exact error I sat with in 2026, when the 4.4-crore file was right about the player and wrong about nearly every other price.

One technical point earns its place here. Modern ODIs use two new balls, one from each end, so at the halfway point the ball is only 25 overs old; seam and swing persist far longer than in the single-ball era. Pakistan's entire collapse sat inside that window — three wickets inside seven overs, the fifth at 13.1 — when both balls were nearly new. That phase tests decision-making more than technique: which ball to leave, which line to merely defend, when even a single is not required. Pakistan failed that test three times, and each time for single figures.

The resource ledger

Three hundred balls allotted, 153 used, 147 unused — 49 per cent of the resource unspent. The team strike rate was 71.9, 110 off 153 balls, against a modern competitive benchmark near 90. Two separate losses occurred and they should be separated.

The first is time: 147 balls wasted. The second is rate: had Pakistan batted the full 300 balls at their own 71.9, they would still have reached roughly 216. Losing wickets was one problem; their own scoring speed was another. When a side is bowled out for 110, everyone asks how they fell. The harder question is what they were doing before they fell.

The answer sits in the lines nobody reads. Hasan Nawaz 17 off 31 (SR 54.8, one six). Salman Ali Agha 9 off 14 (64.3). Arafat Minhas 10 off 18 (55.6). Together: 36 runs off 63 balls, a combined strike rate of 57.1. These were the three men carrying the rebuild, the entire four-to-seven structure. When the rebuilders are all operating below 60, the collapse is not only a bowling achievement but a failure of batting priority. Thirty-one balls for eleven runs outside a six, in a 50-over game, cannot be defended in any conditions.

The boundary dependency makes the dot-ball problem visible. Recorded boundaries — five fours and three sixes — account for 38 runs, at least 34.5 per cent of 110. The other 72 runs came off 145 balls, roughly 2.98 runs per over of non-boundary scoring. That number tells you Pakistan had no rotation mechanism in the middle overs. When nothing but boundaries is coming, the bowler carries no risk; he can hit a sixth-stump line ball after ball because he knows only the batter is exposed.

The partnership arithmetic is self-explanatory. The fifth wicket fell at 61, the innings ended at 110, so the last five wickets added 49. No stand in this innings can have exceeded the mid-forties — that is arithmetic, not estimation. And when that happens, the lower order arrives hoping for an open field and finds an attacking set instead. Shaheen Afridi made 15 off 13 at a strike rate of 115.4 with two sixes; useful, and also a signal — Pakistan's second-fastest scorer was the captain and fast bowler, not a batter.

Babar's 29: the best and the bitterest innings

Babar Azam made 29 off 33 with five fours, a strike rate of 87.9, above the team's 71.9, and the top score. Individually it was not a flawed innings. Structurally it is the harshest fact of the match: no other batter passed 20. A top score of 29 in a completed ODI innings is not one man's failure; it is evidence that the side's best technician was left to defend rather than build, with nobody able to bat alongside him.

This is where I fill the column the model cannot see, and it is always full. In this innings its name is: the batter who stands with Babar. Pakistan needed a number four or five who could walk in at 61-5, bat thirty overs and make sixty at a strike rate of eighty. They did not have one. That vacancy is not one match old; it is a selection-structure vacancy, refilled experimentally every series. Eshan Malinga took Babar's wicket, and with it the innings settled permanently into the 61-5 cluster from which no return was available.

Shadab's swing: narrative versus data

Shadab Khan had made his maiden ODI century against England in the previous match. Here he made 2 off 5, dismissed by Arachchige's off-spin. This is the cleanest narrative-versus-data case in the dataset — the small-sample whiplash that drives selection error at board and media level alike.

Shadab's identity is a spin-bowling all-rounder, not the batter who rescues 61-5 against two spinners. Asking that profile to do that job is a squad-structure error, not a Shadab error. If the team slots him at six or seven and demands a forty-over rearguard, it is misusing his capacity, and that is solved by role definition rather than by dropping him.

Madushanka's five-for: praise with conditions

Dilshan Madushanka: 5-34 in 8.3 overs, economy 4.00, a bowling strike rate near 10.2 balls per wicket. In ODI terms an economy under 5.5 and a strike rate under 30 are both excellent. These are match-winning figures.

The composition still needs reading. Two of the five were Haris Rauf and Shaheen Afridi — tail-enders. The other three were frontline batters, so dismissing this as tail cleanup would be wrong too. The fair reading: a genuine but still incomplete breakout signal. Until I have his new-ball spell — how many inswingers, how much seam movement, on which line — it is not yet evidence of a repeatable top-order skill.

The market will overshoot, because left-arm pace is a scarce archetype and one of the most reliably overpriced in franchise auctions. Every transfer window is a spreadsheet pretending to be a story. This spell is a story about the ODI new ball, not about T20 death bowling, and conflating the two is exactly the imported-framework error I keep catching myself in.

Sri Lanka's structure, fitted to Pakistan's weakness

This is not only a story of Pakistan collapsing; it is a matchup story. Sri Lanka's attack carried three distinct trajectories: left-arm pace (Madushanka), left-arm spin (Wellalage), off-spin (Arachchige). That triangle is the mix that most exposes a top order short of time in the middle. Shadab fell to Arachchige's spin, Hasan Nawaz to Wellalage's — the squeeze came from both ends, not from one spell.

So Sri Lanka's win should be explained as two ends asking different questions, not as Pakistan disintegrating. One spell breaking an innings is fortune. Two ends applying different trajectories is a structure. The latter repeats, which makes it a sustainable tournament model — provided the batting can chase 300-plus, of which this data offers no proof.

Bench-level attribution: Maaz and Saad

Maaz Sadaqat made 8 off 11; Saad Baig 5 off 8. On the surface, two failures. Both walked in after three wickets had fallen inside seven overs, with the ball moving and the field set. Producing 72.7 and 62.5 strike rates in that entry condition is plausible output, not failure output. Their selection is itself a policy — youth blooded inside competitive fixtures rather than low-stakes series. That policy is arguable, but discarding it on one innings repeats precisely the volatility that produced Shadab's century-then-two cycle.

Shaheen's captaincy: a structural conflict

Shaheen Afridi captained and was also Pakistan's second-fastest scorer. A fast-bowling captain in ODI cricket carries a standing conflict: his own ten-over workload, his spell planning, and simultaneously the field settings and bowling changes. This data can flag that conflict, not resolve it. I have no field-placement or bowling-change information, because Pakistan did not bowl in this report. I do not rule on what I do not have.

The contrarian angle: the headline chose the wrong record too

"Pakistan's second-lowest ODI total in Lahore" is accurate and misleading. The venue's absolute lowest is 75, made in 2026 in the second innings. 110 is not an all-time venue record. What 110 is: Pakistan's lowest batting-first total at this ground. That is the meaningful line, because it removes the toss-and-conditions defence.

The real story is not the record but the recurrence. 75 in 2026, 102 in 2026, 110 in 2026 — Sri Lanka the opponent each time, this venue each time. Roughly sixteen years, multiple squads, captains and coaching staffs, same outcome. One bad evening is not a diagnosis; a collapse repeated across three eras is. I press this because the domestic reflex will blame talent and intent, while the data points at new-ball survival and middle-overs rotation.

And the sharper contrarian point: the biggest risk here is not 110, it is the reaction to it. If Maaz Sadaqat and Saad Baig are dropped on one innings, Pakistan repeats the instability that turned Shadab from star to suspect in a week. A side that has collapsed the same way for sixteen years does not need two teenagers removed; it needs the number four role defined.

One more thing must be said plainly: this dataset contains no Pakistan bowling figures. A "crisis in every department" conclusion is unsupported. The recorded damage is batting-only. Keeping it there is analytical honesty, and it is the column the model cannot see.

What to watch next

If Pakistan bring a specialist anchor to number four in the next three home ODIs — a man who can bat thirty overs rather than a fourth all-rounder — Lahore has been read as a process failure, not bad luck. If the same structure repeats, 110 was policy.

In Madushanka's next two ODIs I will watch the new-ball spell, not the wickets. Top-order wickets validate the five-for as a skill signal. Economy above 5.5 with wickets confined to the tail means Lahore was a good evening and little more.

The most important tracker is Shadab's batting position. Above six or below seven tells you whether the team values him as a batter or as a bowler who bats — and from that single slot, Pakistan's whole middle-order plan can be read.

147 deliveries lay on the ground and nobody picked them up. Next time the Lahore scoreboard shows five down near 60, the question will not be what the pitch did. It will be who stood at number four, and what role he was picked for.