110 in 25.3 Overs: Auditing Pakistan's Batting in Lahore, Where Wickets Outnumbered Runs

25.3 overs. 110 runs. Ten wickets. At Gaddafi Stadium, Lahore, Pakistan's innings ended with 24.3 overs unused. The scoreboard said all out. The audit question is why a host side could not last half its allocation.

Stage-1 did not give me the date, the series name, the third team, the second-innings score or the result. What it gave me was a 153-ball scorecard: 110/10 in 25.3 overs, Babar Azam 29, Hasan Nawaz 17 off 31, Shaheen Afridi 15 off 13, Dilshan Madushanka 5/34 in 8.3 overs. My pre-registered hypothesis, one sentence: this reads as a wickets story before it reads as a slow-pitch story; Pakistan's batting process was beaten technically by the new ball and early middle overs, and the real cost of 110 is the 24.3 overs left unused.

| Metric | Data | Audit note | |---|---|---| | Innings | 110/10 in 25.3 ov | 24.3 ov unused | | Run rate | 4.31 | Sub-par before wicket constraint | | Average partnership | ~15.3 balls | No platform | | Top score | Babar Azam 29 | 26.4% of total; failure distributed | | Best bowling | Dilshan Madushanka 5/34 in 8.3 | 4.00 econ, 10.2 balls/wicket | | Result | Unverified | No second-innings data |

Format check first: an 8.3-over spell is impossible in T20; this is ODI. High confidence, rules-based. Source quality is low: every information point is single-sourced and unattributed. The evidentiary base for the conclusions below is medium-low. I numbered the issues because the questions kept outliving the answers.

This is match five of a tri-nation series. A six-match league phase plus a final is the likely structure (three teams × two games = six), which makes this a mid-tournament fixture with table pressure, not a dead rubber. Pakistan lost the toss and batted; Sri Lanka chose to field. Gaddafi Stadium is conventionally a batting-friendly venue with short boundaries, where 300-plus is treated as par. The pitch report, weather, moisture and light data for this match are absent.

The collapse began in the first powerplay and ran through the middle overs. Both openers failed to reach double digits, no substantial partnership formed, and the side was bowled out inside 26 overs. Stage-1 records a name as 'Saif Beg'; this may be a transliteration variant of another squad member, so I will not draw a selection conclusion from it.

The match result is unverified. We have only the first innings. A claim that Sri Lanka dominated is unsupported; there is not one data point from their chase. The tri-series is rare in the calendar, squeezed between the IPL window and bilateral obligations, with limited standalone rights value. Its worth is sporting and reputational, and a 110 at Gaddafi is expensive for the host board's brand asset.

The most expensive part of 110 is the 147 balls never faced. 110 in 25.3 overs is 4.31 an over. Extrapolated to 50 overs at the same rate, Pakistan reach about 215 — sub-par at a venue where 300 is the convention. The larger cost is the 24.3 unused overs, 147 balls. The total is 110; the damage is the 147 balls that were never faced.

Average partnership was 153 balls ÷ 10 wickets = 15.3 balls. No pair lasted three overs on average. That is more than 'no big partnership'; it is no platform. Every time a stand began, a wicket fell.

Read this as a wickets story before a slow-pitch story. On a genuinely difficult surface, sides usually survive longer and score slower. Being bowled out inside 26 overs says the batting was beaten technically, rather than merely contained. The pitch report is absent, so cause is low confidence; the anomaly is high confidence.

The toss explains some of it, not 10 for 110. Pakistan lost the toss and were inserted. Being inserted in seam-friendly morning conditions is a disadvantage. The magnitude of 10 wickets for 110 exceeds what a toss disadvantage can explain. Making the toss the primary cause over-credits luck. Medium confidence.

The host dimension cuts the other way. Visiting sides are the ones who normally struggle with unfamiliar surfaces; Pakistan collapsing at home is a negative outlier against their own home baseline, not proof of structural decline. One innings does not make a trend.

Babar's 29 is a distribution of failure. 29 is 26.4% of 110. A top score of 29 is itself the clearest line in the team's failure. When the leading scorer makes 29, no single batter can be blamed, and no single batter can be credited with resistance. Babar came in at No. 3, played cautiously, got a start, and failed to convert.

His balls faced and strike rate are missing from Stage-1. The public debate around Babar in white-ball cricket is a strike-rate debate; without balls faced, I cannot say he batted slowly or well. Insufficient information, and saying so is the correct audit. Treating 'Babar offered resistance' as proof inflates a 29 into a vindication it cannot carry.

Hasan Nawaz's 54.8 strike rate is a tactical artefact. 17 off 31 is well below the 85-100 range modern ODI Nos. 6-7 are expected to produce. The number describes tactical necessity before technical weakness: in a collapsing innings, occupying the crease has value. His dismissal — losing patience, attempting a big shot, caught — is the decision error. At the 20th-25th over, the required rate was already climbing, so the shot was defensible in isolation. The real miss was earlier, at 20/2 or 30/3, when nobody rotated strike.

If 31 balls produce 17 runs and no partnership holds, the question is not why he played the big shot; it is why strike rotation did not happen before that. Medium confidence.

Shaheen's 15 off 13 is a diagnostic. A frontline fast bowler at No. 9-10 becoming the second-most fluent scorer is not a positive sign. It is a diagnostic of the top seven being comprehensively outplayed. The media habit of framing tail-end runs as resistance softens the top-order failure; it does not treat it. When the lower order looks more fluent than the top seven, that is not proof of batting depth; it is a certificate of top-order failure.

Madushanka's 5/34 is the match-defining number. 5/34 in 8.3 overs, economy 4.00, a wicket every 10.2 balls. He took wickets without being milked, the signature of a bowler who was never allowed to be played out. He delivered 33% of the innings' overs. The left-arm angle against a right-hand-dominant top order is a plausible mechanism, but dismissal modes are not recorded; confidence on the how is medium. An 8.3-over spell is longer than one burst, so he probably returned to break the Hasan Nawaz stand — low confidence. Sri Lanka's attack should be read as a structural asset with a clear plan and the discipline to execute it; that profile travels better than a batting-dependent side.

Opening fragility is the highest-leverage structural question. Both openers failed to reach double digits. That forces Babar to stabilise from ball one, which compresses his scoring intent. The chain is plausible, not proven; selection and team instructions are absent. The Bengaluru desk taught me to read a match sideways: where the scoreboard shows '29', the story is the over in which the No. 3 had to walk in.

A ruptured knee taught me to distrust any system with one point of failure. Opening is that point in Pakistan's batting. I will not assume no alternatives existed; the question is whether a second option was available and unused. Stage-1 has no selection data, so the question stays open.

The result is unverified, so the audit is incomplete. We know only the first innings. Whether Sri Lanka chased comfortably or suffered their own collapse is unrecorded. A 'Sri Lanka dominated' frame is unsupported. If Sri Lanka also collapse under 150, the story becomes conditions or systemic failure; if they chase comfortably, it becomes a Pakistan-specific batting failure. Both possibilities remain open, and a report that fixes one is not doing its job.

One governance-adjacent question follows: the host board's pitch preparation. A home side bowled out for 110 at its own venue invites legitimate questions about curator instructions. There is no pitch report, so this is a question, not a finding. There is no integrity signal; a 110 all out is not an ACU flag by itself.

The easy read is that Pakistan batted badly. It may be right. It stops at the total. The media frame 'barely reaching a hundred' centres 110; my counter centres 24.3 unused overs and a 15.3-ball average partnership. 110 is the symptom; 147 balls never faced is the condition.

Babar's 29 as resistance is a dangerous frame; it hides the distribution of failure across the unit. Shaheen's 15 as a fight softens the top-seven failure. Both readings make the copy warmer and the audit weaker.

I am recording the concession in advance. If the next three or four scorecards show Pakistan losing two or more wickets in the first 10 overs and an average partnership under 20 balls, this is a trend; the consensus will be right. If a pitch report shows moisture or seam movement and Sri Lanka also collapse under 150, the conditions thesis strengthens. Without those checks, my technical-failure frame is incomplete.

One more blind spot: we are auditing a match whose result we do not know. The audit is incomplete; calling it incomplete is the honest position. Pre-registration is how I keep hindsight from wearing a victory lap.

Next match, watch three variables before the scoreboard: wickets in the first 10 overs, the over in which Babar arrives, and the split of Madushanka's spell. If Pakistan's opening lasts 15 overs, 110 becomes a bad morning; if it does not, it is a system habit. Does anyone have a second option, or is everyone waiting for the scoreboard?