The 110 Audit: Why Pakistan’s Innings Ended in 25.3 Overs in Lahore

One line in a scorecard can flip the story of a match. At Gaddafi Stadium, Lahore, Pakistan’s innings ended at 110 in 25.3 overs — 153 balls, 10 wickets, and 24.3 overs unused. This is not merely a low score; it is a budget in which less than half of a 50-over allocation was spent. At 4.31 runs per over, a full 50-over innings would have reached roughly 215 — itself below contemporary ODI par. The real cost is not 110 but 110 with 24.3 overs left unused. I opened my Salt Lake notebook and placed the scorecard beside it. The habit is old: first write what the ground showed, then reconcile it with the record. The available brief records no date, no series name, no third team, no result and no source attribution. So the first task is to set the boundary. Dilshan Madushanka’s spell is logged as 8.3 overs. A bowler cannot bowl more than four overs in a T20. A tri-nation series and a single-innings scoreline make this an ODI. That is a rules-based inference, not a commentator’s memory. The methods note must stay visible. This report covers the first innings only. There is no second-innings score, so writing ‘Sri Lanka dominated’ or ‘Pakistan lost’ would be dishonest. There is no pitch report, no weather, no dew, no DRS reference. What exists is this: Pakistan lost the toss and batted first, made 110 in 25.3 overs at home, and one left-arm seamer took 5/34 in 8.3 overs. Questions should stay inside that boundary. The first signal is not the score but the overs. Leaving 24.3 overs unused in a 50-over match suggests the innings was not stalled by a slow pitch; it was broken by wickets. On a genuinely difficult surface, batters usually survive longer and score slower. Here the opposite happened: 10 wickets fell in 153 balls. Average partnership length was about 15 balls. No pair survived even three overs on average. The second signal is the opening stand. Neither opener reached double digits. That is not a small detail. When openers cannot pass ten against the new ball, the No. 3 — Babar Azam — is forced into stabiliser mode from ball one. His scoring intent compresses, and the powerplay budget suffers. Babar made 29, 26.4% of the team total. It is the top score, and also the harshest statistic: when the leading scorer makes 29, the failure belongs to the top order, not to one batter. This is where possession and control separate. Boundary share in the powerplay is possession. Wickets in hand against required rate is control. Pakistan never established the first, and the second never appeared. Ten wickets for 110 is not a case of losing control; it is a case of never establishing it. Hasan Nawaz’s 17 off 31, strike rate 54.8, is the most debated data point. Occupying the crease can have value in a collapse. But by the 20th to 25th over, the required rate was already climbing; his dismissal — losing patience, attempting a big shot, caught — was a decision error, not a technical one. The earlier failure was at 20/2 or 30/3, when nobody rotated strike. Shaheen Afridi’s 15 off 13, strike rate 115.4, is not a comfort. It is a diagnostic. When a frontline fast bowler batting at No. 9 or 10 becomes the second-most fluent scorer, the top seven were comprehensively outplayed. Tail-end runs are often misread as resistance. Here they are a certificate of top-order failure. Dilshan Madushanka’s 5/34 in 8.3 overs, economy 4.00 and strike rate 10.2 balls per wicket, is the strongest data point in the report. An economy of 4.00 means he took wickets without being milked. That is the signature of a bowler who was never allowed to be played out. He delivered about 33% of the innings’ overs. The left-arm angle against a right-hand-heavy Pakistan top order is a plausible mechanism, but dismissal modes are not recorded. The number is high-confidence; the mechanism is medium-confidence. Gaddafi Stadium is conventionally a batting-friendly venue where 300-plus is a par first-innings score. A 110 all out there is an anomaly. Three explanations are possible: a fresh or damp surface, pronounced seam or swing in the morning, or simply poor batting. The brief has no pitch report, so none can be declared the final truth. But one point holds: a home side collapsing at home weakens the excuse that only visiting teams misread conditions. The toss is another easy excuse. Pakistan lost it and were inserted. New-ball movement can disadvantage the side batting first, but 10 wickets for 110 exceeds what a toss disadvantage can explain. Over-crediting luck here would be the reverse of luck-stripping: using fortune to mask technical failure. Now the part where the data does not become a verdict. One innings cannot establish that Pakistan’s ODI batting is in decline. A trend needs the surrounding three to five innings. Babar’s balls faced and strike rate are missing, so claims that he ‘anchored too slowly’ or ‘batted well’ are both incomplete. The identity of ‘Saif Beg’ is unclear and must be verified before any player-level conclusion. Madushanka’s 5-for mechanism is inference, not proof. And with no second-innings data, no result can be asserted. A small pattern kept returning, so I stopped calling it noise: Pakistan’s problem centres on the start of the top order. Both openers under ten, average partnership 15 balls, Babar stabilising from ball one. That chain can repeat. If the next match also passes ten overs without a partnership lasting 25 balls, ‘bad day’ becomes harder to defend. In commercial terms, the tri-series format itself is fragile. With the calendar dominated by the IPL window and bilateral commitments, tri-nation ODI series are rare and commercially marginal; they often function as preparation vehicles. For the host board, a 110 at a redeveloped Gaddafi Stadium is not only a defeat but a product failure. For Madushanka, the spell raises visibility, but an ODI five-for does not automatically translate into T20 auction value; the formats reward different skills. On governance and integrity, there is no signal. A 110 all out is not, by itself, an anti-corruption flag. ACU red flags concern abnormal betting patterns and specific-event manipulation, not team totals. The legitimate governance-adjacent question is host pitch preparation: a home board producing a surface on which its own side is bowled out in 25.3 overs invites scrutiny. But with no pitch report in the brief, that remains a question, not a finding. The notebook recorded the scene; the data recorded the shift. The scene was Pakistan folding early in Lahore. The data says the collapse was not only about 110 but about 24.3 unused overs and a 15-ball average partnership. The next signal will come over the next three innings: how long the opening pair lasts, when powerplay wickets fall, and what situation Babar inherits. If the chain repeats, this stops being a bad day and becomes a selection and preparation problem.