110 in Lahore: The 147 Unused Balls Tell What the Scorecard Cannot

The biggest number at Gaddafi Stadium that evening was not 110. It was 147.

When the last batter walked back after 25.3 overs, one whole column of the scoreboard had never been used: twenty-seven overs and three balls of a fifty-over game, one hundred and forty-seven deliveries that never reached the pitch. I was watching a stream in the slanted early light of a Bangalore morning, and when that empty space appeared on the board, my attention moved from the runs to the absence of them. Cricket counts the runs made; it rarely counts the runs never attempted — and the second number is usually the more honest one.

That is why this innings cannot be dismissed as '110 all out'. It never reached its second phase. A fifty-over innings has anatomy: build from eleven to forty, launch from forty-one to fifty. Pakistan reached neither. It collapsed at the door. At Derby, I found the story hiding beneath the word count; in Lahore I found the same thing hiding beneath the score — the time a team did not spend, and the time it wasted.

Two figures capture the whole character of the innings: a team strike rate of roughly 71.9 (110 off 153 balls), and three wickets inside the first seven overs. Modern competitive one-day sides sit around 90. Seventy-one is not merely slow batting; it says the batters endured deliveries rather than winning them. And when you endure, wickets fall, because the bowler gets to land six or seven balls in the same place.

I do not know what the pitch was doing, and I am saying so deliberately. The match report this piece is built on carries no pitch report, no weather detail, no post-toss conditions, and no outcome for Sri Lanka's chase. Without that, calling 110 the work of the surface or the work of the batters is dishonesty. What can be said is this: whatever the conditions, one team used less than half of the resource it had. Resource wastage is always a technical question, never an alibi.

This was match five of a home tri-series for Pakistan. They chose to bat, and that detail will be the most misread of all. Because after a defeat everyone will say batting first was the wrong call. That cannot be proved from this data. To judge the decision you need to know what Sri Lanka scored on the same pitch, at what rate, for how many wickets. Without that, 'batting first was wrong' is treating consequence as cause — the oldest error in cricket analysis.

The squad picture is clearer. Shaheen Afridi captained — a fast bowler who must also bowl ten overs, set fields, change bowlers and bat lower down. Four roles on one man is a structural problem, not a personal one. The top order carried Maaz Sadaqat and Saad Baig, 8 off 11 and 5 off 8. Those numbers settle nothing; they only record that two inexperienced batters were at the crease while the new ball was moving and wickets were falling.

Sri Lanka's attack was built to meet that weakness directly: left-arm pace from Dilshan Madushanka, left-arm spin from Dunith Wellalage, off-spin from Sahan Arachchige. Three trajectories, three angles. For a batter whose feet have not settled, that is the hardest kind of siege, because he must change rhythm three times before finding one. Madushanka took 5-34 in 8.3 overs — economy 4.00, a wicket roughly every tenth ball. Excellent figures. But at least two of those five were Haris Rauf and Shaheen Afridi, tail-enders. It is not yet proof of a repeatable top-order-breaking skill. Lord's in 2026 taught me that: a notebook, a deadline, and a quieter truth — one evening's five wickets is a page in a player's journey, not his passport. Left-arm pace is a scarce commodity, so the market will over-price this spell; his next two new-ball spells will say more than the wicket count.

Look at the shape of the collapse. Fakhar Zaman 5, Maaz 8, Saad 5; three down inside seven overs; 61 for 5 at 13.1. This was a failure of the head, not the tail. If you slide from 200 for 4, the problem is middle-overs spin pressure and lower-order capacity. If three wickets go inside seven overs, the problem is technique and decision-making against the new ball. Different diseases, different cures.

Babar Azam's 29 off 33, five fours, strike rate 87.9, was both the best and the saddest number of the match. Best because it was above the team's 71.9; saddest because a top score of 29 in a completed innings means the side's finest technician was sent to defend rather than to build. He fell inside that 61 for 5 cluster, to Eshan Malinga, and the innings sat down where it stood. That is not Babar's failure. It is the failure of a team that has no second anchor.

Salman Ali Agha 9 off 14, Arafat Minhas 10 off 18, Hasan Nawaz 17 off 31 — three middle-order innings below a strike rate of 65 in a match that needed runs. Hasan Nawaz's is the most telling: 31 balls, one six, and eleven runs off the other thirty. A number seven who is set in a fifty-over game is expected to strike above 90. He survived without scoring. Surviving and scoring did not happen together.

At least 38 of the 110 came from the eight boundaries explicitly recorded — 34.5 per cent of the total — with the rest arriving at well under four an over across more than 120 balls. That is the dot-ball problem, and it is less about run-making than about the absence of a plan. No partnership of substance can have existed: the fifth wicket fell at 61, the innings ended at 110, so no stand plausibly passed the mid-forties. Without a platform, the lower order always faces an attacking field.

Shadab Khan is the fastest lesson in the whole report. A maiden ODI century against England, then 2 off 5, dismissed by Arachchige. In five days he will have gone from 'arriving as a batter' to 'finished'. Both are wrong. He is a spin-bowling all-rounder with high batting variance, and asking that profile to rescue 61 for 5 against two spinners is a squad-structure problem. Strike rate in cricket now plays the role xG played in football: it tells you what happened, not why. Reading one innings as form is the same error in both directions.

And Shaheen? As captain, his innings ended in 25.3 overs. As a batter, he made 15 off 13 at 115.4 with two sixes — Pakistan's second-most effective scorer by rate. The contradiction revives a structural argument Pakistan keeps forgetting. This report contains no field-setting or bowling-change information at all, so judging the captaincy would repeat exactly the mistake we made with the batters.

Now the part where everyone should pause. The headline calls this Pakistan's second-lowest ODI total in Lahore, and it merges two different records: the venue's all-time low and the lowest batting first. Pakistan's lowest at Gaddafi is 75, made in the second innings against Sri Lanka in 2026. 110 is the lowest batting first. The second matters more, because batting first means the collapse came without scoreboard pressure, on their own terms.

More important still is the pattern: 75 in 2026, 102 in 2026, 110 now — all against Sri Lanka, all at this ground, across three different squads. The recurring signature is Pakistan's inability to absorb Sri Lanka's new ball at this venue. That converts a bad afternoon into a diagnosis, and it is not a talent problem in the abstract.

One silence deserves naming. The report carries no detail of Sri Lanka's chase — no wickets, no overs, no rate. Short match reports routinely omit one-sided chases, so the silence weakly suggests the result was never in doubt. That is an argument from omission, not evidence, and I will not dress it up as more.

Same with the toss. Whether 110 was par, below par, or unplayable on that surface cannot be established without Sri Lanka's innings. Those who stamp the decision as wrong are converting outcome into cause.

And the young batters are about to be misused. Maaz's 8 and Saad's 5 will be cited as proof they are not ready, though they walked in at three down inside seven overs with the ball moving. Demanding that a player prove himself in his first exposure is not only cruel, it is technically self-defeating: a batter who believes one false shot decides his career shrinks his backlift and raises his risk. We have seen it repeatedly in comeback matches.

Is this a crisis across all disciplines? No, and this is the essential finding. The report contains not one Pakistan bowling figure — no over, no wicket, no economy. The damage recorded is batting-only. What is true is that Pakistan's ODI batting depends on Babar to a degree that makes 110 a predictable outcome when his top score is 29. The absence of a second anchor at four or five is the structural issue, not his output.

For Sri Lanka, the win rests on bowling: ten wickets shared by five bowlers, including a left-arm quick's five-for. That is a sustainable tournament model but a fragile one — it says nothing about chasing 300 when the ball stops moving. Their three-trajectory attack is a template for the rest of the tri-series, because it is the cheapest weapon against a brittle top order.

In more than fifty years of watching, I have learned that the most misread moment in cricket is a good team's bad collapse, because the national mood sets the analysis. The year the noise stopped, I heard the game breathe — 2026, empty stands, an air-conditioner humming in a vacant press box. Strip the noise from Lahore's 110 and listen to what remains.

What remains: three wickets in seven overs; 61 for 5 at 13.1; no partnership of substance; seven of ten dismissed batters making nine or fewer; the top three aggregating 18 off 32; a team strike rate of 71.9 while the world plays near 90; and 147 deliveries never bowled. Brisbane taught me to watch the second XI warm up — that night I ignored the winning shot and wrote about Mohammed Siraj's run-up, the pause at the top of his mark. Lahore's story lived in the same place: in the deliveries Pakistan took and gave back.

So what to watch next is not the score. Who bats at four — a specialist anchor means structural correction, another all-rounder means cosmetics. Whether Maaz and Saad are retained, because dropping them would repeat the volatility that produced Shadab's century-then-two cycle. Whether Shaheen has a formal vice-captain planning spells with him. And Madushanka's next two first spells, judged on economy and top-order wickets, not the tally.

My notebook entry for that evening is not a score: 'Gaddafi Stadium, 25.3 overs, and the twenty-seven overs nobody played.' The question is not how small 110 was. It is whether, the next time Pakistan bat first, there is a man on the field whose only job is to survive — leave the ball, play behind the body, stay alive to the thirteenth over. Until he exists, 110 will come again. Perhaps at this ground, perhaps against this team, perhaps sixteen years from now.