Pakistan All Out for 110: The 24.3 Overs Nobody Bowled Are the Real Story

Gaddafi Stadium, Lahore. What the scoreboard showed was a three-digit figure — 110. What entered my notebook first was not the runs. It was the 25.3 in the overs column. A fifty-over match, and the host side could not complete even half its allocation. Twenty-four overs and three balls — 147 deliveries — that were never bowled. It is the quietest kind of loss in cricket, because a ball never delivered leaves no entry in the scorecard. The notebook began where the broadcast microphones stopped. On television, "110 all out" is a result. On the scoresheet, 25.3 is an accusation, and it is levelled not at one innings but at an entire batting unit. One thing needs stating at the top, because my habit is to attach a sample and a source to every claim. The record available for this match is single-sourced, unattributed to any agency, carries no series name, and does not mention the third team. The numbers — 110 in 25.3 overs, and 5/34 in 8.3 overs — are internally consistent, so they do not read as fabricated. The conclusions will stay cautious in proportion. I am reading this innings as evidence, not as a verdict. Format identification is a matter of rules, not inference. An 8.3-over spell is impossible in a T20, where the cap is four overs. So this is a fifty-over match. The fifth fixture of a tri-nation series, meaning the middle of a round-robin, where the points table already exists and every result reshapes the arithmetic ahead. Host Pakistan lost the toss and were inserted. Lahore's surface has historically favoured batting, with short boundaries, where 300 is treated as a par first-innings score. Being bowled out for 110 at a ground of that type is a statistical anomaly, and an anomaly leaves only two explanations: either the surface was fresh with residual moisture, or the batting was technically beaten. I have no pitch report, so I cannot adopt the first cause — but the second is available to me from the scoresheet. The arithmetic is plain. Ten wickets in 153 balls means an average partnership of roughly fifteen deliveries. No pair survived even three overs on average. That figure says wickets fell at regular intervals rather than in a single clatter. When wickets scatter like that, the story is not a slow pitch but a beaten technique. On genuinely difficult surfaces sides usually last longer and score slower; being wrapped up inside twenty-six overs is evidence that the bowlers did not contain, they defeated. The run rate was 4.31. Contemporary ODI scoring at Pakistani venues sits between 5.5 and 6, so this is roughly a run and a half below par. Extrapolated over fifty overs at the same rate, the total would have been about 215 — itself sub-par. The real cost is therefore not "110" but "110 with the innings truncated." The bitterest number in this innings is not the total but the top score. Babar Azam came in at No. 3, tried to play cautiously, got a start and failed to convert — 29 runs, 26.4 per cent of the team's total. When the leading scorer makes 29, the failure is distributed: no single batter can be blamed, and equally none can be credited with resistance. "Babar showed some fight" is a correct sentence, but it cannot be inflated into a vindication of his approach. And one thing the record does not carry: how many balls he faced. The entire public argument about Babar in white-ball cricket is a strike-rate argument. Without balls faced, both "he batted too slowly" and "he batted well" are unsupported. My notebook says plainly: insufficient information. Hasan Nawaz's 17 off 31, a strike rate of 54.8, is a tactical artefact rather than a technical one. Occupying the crease during a collapse has real value. His dismissal — losing patience, attempting a big shot, caught — was the decision error, though in isolation the shot was defensible, because by the twentieth to twenty-fifth over the required rate had already climbed. The actual miss came earlier, at 20/2 or 30/3, when nobody was rotating strike. Shaheen Afridi's 15 off 13, which the coverage turned into credit for "helping Pakistan reach a hundred," is a diagnosis, not a compliment. When a frontline fast bowler batting at nine or ten is the side's second most fluent scorer, only one reading holds: the top seven were comprehensively outplayed. Framing tail-end runs as resistance is an old and easy mistake. The most analytically significant figure of the match belongs to Dilshan Madushanka: 5/34 in 8.3 overs. An economy of four and a strike rate of 10.2 balls per wicket. That is the real story. It means he was taking wickets without being milked — he was never allowed to be played out. He delivered one-third of the innings' overs by himself. Left-arm pace against a right-hand-heavy Pakistan top order is a known and recurring vulnerability, though the modes of dismissal are not recorded, so I will stay cautious about the mechanism. Now the part where outside opinion turns the wrong way. The first excuse is the toss. Pakistan lost it, were inserted, and being inserted in morning moisture is a genuine disadvantage. But ten wickets for 110 exceeds what a toss disadvantage can explain. Treating the toss as the primary cause lends luck the credit that a technical failure should be paying for. The second excuse inverts the logic of home advantage. Visiting sides are the ones who normally struggle on unfamiliar surfaces — here the host side collapsed on its own. For a team that looks this weak at home, blaming the pitch is a weak argument. And the third error, the most widespread: "Sri Lanka dominated." I have only the first innings. Whether Sri Lanka chased comfortably or struggled themselves is unknown. Before converting the result into a story of dominance, the second-innings scorecard needs reading. What sounded like noise in the stands was a rhythm I could count — and this innings kept one rhythm: wicket, a few overs, wicket again. The rhythm changed only briefly when the tail held the ball back for a while. What to watch next is clear. One innings does not establish a batting decline; the next three to five innings in sequence are required. The sharpest scrutiny belongs on the opening pair — neither opener reached double digits, and when that happens Babar at No. 3 inherits a stabilising role from the first ball, which compresses his scoring intent. The chain is plausible, not demonstrated. I keep margin notes because the scoreboard has no memory. The next time a side bats first in Lahore, it will be worth checking whether a pitch report is published and what instructions the curator was given. A host board whose own batting order is bowled out for 110 on its own surface can legitimately be asked that question — but asking a question and drawing a finding are different operations. For now the ledger records only this: 25.3 overs, and the twenty-nine that nobody played.