110 in 25.3 Overs: The Lahore Scorebook That Does Not Blame the Pitch

There is one line in the scorebook — 25.3 overs. The column after it is blank. Pakistan all out for 110, 24.3 overs unused, and on the other side of the card Dilshan Madushanka: 8.3 overs, 5 wickets, 34 runs. Gaddafi Stadium, Lahore. Before I look at the total I look at the overs column, because that is what tells you how an innings actually ended. A 110 in fifty overs can be the story of a slow pitch. A 110 in 25.3 overs is the story of wickets. I learned this beat from the steps, not the press box — and on the steps I also learned not to write down what I did not see. The first task is verification. The record in front of me carries no date, no full series name, no mention of the third team, and no result. What it does carry: match five of a tri-nation series, Gaddafi Stadium, Pakistan inserted after losing the toss, innings terminated at 25.3 overs. The format leaves exactly one hard clue — a spell of eight and a half overs. A bowler is capped at four overs in a T20 and four in The Hundred. That length is possible only in an ODI or a Test; a single-innings scoreline plus a tri-series structure settles it as a one-day international. Check the timestamp before you check the source, and the format before the timestamp — thirty years of paper taught me that order. Match five of a round-robin matters. Three teams playing each other twice makes a six-match league, which means this was a fixture with table consequences, not a dead rubber. Pakistan were the hosts. Lahore is conventionally a batting venue — short boundaries, 300-plus a par first-innings score. Against that baseline, 110 all out is an anomaly rather than proof of a structural batting decline. A home side folding at home cuts against its own baseline, and that is the cleanest fact in the file. The record does not say what the pitch was doing. No pitch report, no weather note, no dew reference. Two explanations survive — early seam movement on a fresh or damp surface, or straightforwardly poor batting. I cannot separate them, so I do not. The document does not blink, and that is exactly why I keep it: it does not let me finish a story with a guess. What can be counted, I count. 110 runs in 25.3 overs is a run rate of 4.31. Contemporary ODI par at a Pakistani venue runs roughly 5.5 to 6, so this innings sat about a run and a half per over below standard. Carried across fifty overs at the same rate, Pakistan reach about 215 — itself sub-par, but better than 110. The real cost is not the 110. The real cost is 110 with the innings truncated. Those 24.3 unused overs are the price. Ten wickets, 153 balls — an average partnership of about 15 deliveries. No pair survived three overs on average. Both openers failed to reach double figures. The consequence is that Babar Azam, at No. 3, had to stabilise from the first ball, which compresses scoring intent by default. The chain is plausible, not proven, because his balls faced are not in the record. Babar's 29 was the top score, 26.4 per cent of the total. Television will call it resistance, and technically that is fair. But the statistic that stings is not the 110 — it is a top score of 29. When the leading scorer makes 29, the failure is distributed: no single batter can be blamed, and equally none can be credited with holding the innings. His balls faced are missing, so any verdict on his strike rate — too slow, or well judged — is unsupported. Insufficient information, stated plainly. Hasan Nawaz: 17 off 31, a strike rate of 54.8 against a modern ODI benchmark of 85 to 100 for a No. 6 or 7. In a collapsing innings, occupying the crease has genuine value, so this is a tactical artifact more than a technical fault. The error was the dismissal — losing patience, going for the big shot, caught — and even that was defensible with the required rate already climbing. Shaheen Afridi's 15 off 13 at 115.4 is the opposite kind of data point. A frontline fast bowler being the second-most fluent scorer is not encouragement; it is a diagnosis. Framing tail-end runs as resistance is an old press-box habit. The scorebook files them as evidence of a top-order failure. The heaviest number in the file is Madushanka's 8.3-5-34. An economy of 4.00 and a wicket every 10.2 balls means he was taking wickets without being milked — the signature of a bowler who was never allowed to be played out. He accounted for a third of the innings. The left-arm angle against a right-hand-heavy Pakistan top order is a plausible mechanism, but the dismissal modes are not recorded, so I trust the number fully and the mechanism only partly. Now the part where the easy outside conclusions break. First, the toss. Pakistan lost it and were inserted, which is a genuine disadvantage against morning seam. But ten wickets for 110 is larger than a toss can explain. Treating the toss as the cause over-credits luck and under-credits technique. Second, the pitch excuse. Visiting sides are the ones who struggle on unfamiliar surfaces; the host folding for 110 at home weakens any pitch-based mitigation rather than strengthening it. Third, and most important: the result is not in the record. I have a first innings and nothing else. Whether Sri Lanka chased comfortably or stumbled themselves is unverified, so any framing of Sri Lankan dominance is assumption, not reporting. The question ahead is not whether Babar made 29. The question is that the opening pair did not reach double figures, and what the selectors do about it. One innings cannot establish whether Pakistan's ODI batting is declining or this was a bad day; that needs the three to five innings around it, which my binder does not yet hold. The next four scorecards will settle it, not the next press conference. And one thing that does not follow from Madushanka's 5/34: a strong ODI spell does not by itself create T20 auction value, because the two formats reward different skills. Whoever erases that distinction will be opening his binder next season.