Pakistan All Out for 110: The Real Story Is the 147 Balls That Were Never Bowled

The last wicket fell at Gaddafi Stadium and the board said 110, with 25.3 overs written beneath it in smaller type. In the press box the young reporter beside me began typing '110' into his copy. I leaned over and said: put the overs in too. Because the biggest event of that evening was not the 110 runs. It was the 147 balls that were never bowled. In a fifty-over match, a side finished its innings with twenty-four point three overs still in hand — it did not even use half its allocation.

Five decades of watching this game have taught me to look in the same order every time: first at what did not happen, then at what did. In an empty stadium you can hear the grass grow — and in the unused overs you can hear every weakness of a batting unit at once. The press room went quiet before the stadium did that evening.

One accounting note before anything else, because the generation sitting next to me sources its facts from a feed and I am the old man who asks for the attribution. The match report this analysis rests on carries no date, no series name, no third participating team and no source line against any of its facts. The numbers it does give — 110, 25.3 overs, 5/34 — are internally consistent, and there is no reason to treat them as invented. But not one of them is corroborated by a second, independent source. Where I am inferring, I will say so plainly.

Start with the format, because that is where every downstream misreading begins. Dilshan Madushanka's spell is recorded as 8.3 overs. A bowler is capped at four overs in a T20 and four in The Hundred; a spell of eight and a half overs exists only in a fifty-over game or a Test. Add a tri-nation series and a single-innings scoreline and the format is settled. Anyone filing this innings as T20 form will get the entire story backwards.

Now the ground. Gaddafi Stadium, Lahore. Pakistan were the hosts. Lahore is conventionally a batting surface with short boundaries, a place where anything under 300 in the first innings is treated as an anomaly. Pakistan lost the toss and were inserted. This was the fifth match of a three-team round robin — six league fixtures plus a final — so it carried table consequences rather than dead-rubber status. The psychological cost of a collapse is higher in a live fixture.

Which brings me to the notebook I carry to every training session, the page headed 'Three things I saw.' That evening all three pointed the same way.

The first was the arithmetic of partnerships. 153 balls bowled, ten wickets down. That is a wicket roughly every fifteen balls. No pair survived three overs on average. That matters. When a side collapses properly, there is usually one stand that drags the innings along — a thirty- or forty-run partnership bridging the gap between the first and second spells of the quick bowlers. There was no bridge here. Wickets fell at regular intervals rather than in a heap, and regular-interval wickets point less at one bowler's magic and more at a collective technical failure.

The second was the rate: 4.31 runs per over. Contemporary one-day par at a Pakistani venue sits around 5.5 to 6. That is a run and a quarter to a run and three-quarters below par. Extrapolated across fifty overs at the same rate, Pakistan reach roughly 215 — itself inadequate. But the real damage is not the 110. The real damage is that while scoring 110, the side also burned 147 balls. Runs and balls are separate assets in cricket. A team bowled out for 110 having used the full fifty overs at least buys time, ages the ball and builds some pressure. Pakistan did not buy any of that.

The third, and the most analytically useful item in the whole report: Madushanka's 8.3-4-34-5. An economy of 4.00 alongside a strike rate of 10.2 balls per wicket. Reading those two numbers separately is the classic error. In ODI cricket, par economy is roughly 5.5 and par strike rate roughly 30 balls per wicket. Madushanka took wickets without being milked — the signature of a bowler who never let a batter settle. He delivered a third of the innings' overs. The left-arm angle against a right-hand-dominant Pakistan top order is a familiar, recurring structural vulnerability. This was not a spell that broke the match; it was a spell that defined it.

Now the individual lines, and here I exercise the discipline my own rules demand. Babar Azam made 29, which is 26.4 percent of the total and the top score. When a side's leading scorer makes twenty-nine, the failure is distributed — nobody can be blamed and, equally, nobody can be credited with resistance. The report says he tried to play cautiously, got a start and did not convert. That is accurate; it should not be inflated into a vindication of his method. And the number that underpins the entire public argument about him — balls faced — is absent. Without it, any claim that he anchored too slowly, or batted well, is unsupported.

Hasan Nawaz made 17 off 31, a strike rate of 54.8. A modern ODI number six or seven operates between 85 and 100. Fifty-four point eight is severe — but the raw number misleads without context. Occupying the crease in a collapsing innings has real value. His error was a decision, not a technique: he lost patience, went for the big shot and was caught. At that stage the required rate was already climbing, so the shot is defensible in isolation. The failure was earlier, at 20 for 2 or 30 for 3, when nobody was rotating strike.

And Shaheen Afridi: 15 off 13, a strike rate of 115.4, credited with helping Pakistan past a hundred. That is a diagnostic, not an achievement. When a frontline fast bowler batting at nine or ten is the second most fluent scorer in the innings, the message is that the top seven were comprehensively outplayed. Calling tail-end runs resistance is the most comfortable habit in subcontinental cricket writing, and it hides the truth.

The opening pair: neither man reached double figures. That sentence recurs in Pakistan's white-ball record. When Babar must stabilise from the first ball at number three, his scoring intent compresses. It is a plausible causal chain — and it is inference, not demonstration, from a single innings.

Now the contrarian part, because the outside reading of this match has been wrong in four different directions.

First, the slow-pitch story. On a genuinely difficult surface, sides survive longer and score slower; they do not lose ten wickets inside twenty-six overs. A 110 all out at Gaddafi is not a normal distribution outcome. It may well be that the strip had residual moisture or that there was pronounced early seam movement. But this report contains no pitch report, so that remains a question, not a finding.

Second, the toss story. Being inserted on a fresh surface in seam-friendly morning conditions is a genuine disadvantage — worth perhaps fifteen runs, not ten wickets. Blaming the toss is the same error as crediting luck at the wrong end of the ledger: it lets a technical failure off the hook.

Third, the Sri Lanka domination story. We have only the first innings. Whether Sri Lanka chased it comfortably or suffered their own collapse is unknown, and anyone who did not watch the second innings cannot assert that they dominated.

Fourth, and largest: the claim that this proves Pakistan's one-day side is in decline. One innings does not establish a trend; separating a one-off from a pattern needs three to five surrounding innings, and those are absent. The host-nation dimension cuts oddly against the excuses, because visiting sides are the ones who normally struggle on unfamiliar surfaces. When the home board prepares the pitch — and the PCB does prepare pitches at Gaddafi — a 110 on it raises legitimate questions about curator instructions, residual grass and watering philosophy. That is ordinary accountability, not conspiracy.

The man nobody credited here is the one behind the stumps, up and down for twenty-six overs, whose name will appear in no headline. I have argued for years that the hardest team in world sport is India's second XI; I would add that the most invisible work in cricket is the work that ends up as a single column in the scorebook.

What to watch next. The gate at the next fixture on the same ground: a twenty-six-over innings in a home international damages the ticketing, and an empty stand next time out would tell you the 110 travelled further than the scoreboard. Whether the selectors raise the opening question, because two single-figure scores is a recurring problem rather than a one-match event. And whether the review of this innings happens in six months or is forgotten by next week. I know which answer is coming. I still leave the question in the copy, because the first verdict is almost always the wrong one.

Print deadlines trained me to hear the clock in every sentence. That evening the clock counted 147 balls that were never bowled. Next time someone shows you a scoreboard, ask it for the overs as well.