110 in 25.3 Overs: Behind Madushanka's 5/34, the Lahore Story Is Pakistan's Team Sheet

At Gaddafi Stadium the board read 110 beside 25.3 overs, and the only figure in my notebook was 153 — the balls Pakistan actually faced. A 50-over innings is 300 balls; this one ended at 51 percent of its contracted length. Five days at Eden Gardens taught me the story lives in the chai refill, and here it lived in the moment the scoreboard showed 91/7 at 21.4 overs. The last three wickets added 19, two sixes from Shaheen Afridi among them. Without those 19 the total stops in the nineties and the collapse looks materially worse. Pakistan chose to bat first in match five of the tri-series and were bowled out for 110.

Context: a Lahore wicket where 110 does not fit

Gaddafi Stadium has historically been a batting ground. Even a sub-250 total reads as unusual there, so 110 is an outlier against venue norms. The important detail is what the innings did not contain: no rain, no Duckworth-Lewis revision, no interruption of any kind. This was not a weather-shortened innings. It was a full 50-over innings that stopped at 25.3, which means conditions cannot be offered as the explanation for the collapse.

Through the powerplay-equivalent phase to 6.2 overs, Pakistan were 23/2 at 3.60 an over. The middle block, 6.2 to 21.4 overs, produced 68 runs and five wickets. The tail added 19 runs and three wickets. At no point did the platform phase exist that the final ten overs are supposed to accelerate from. There is a second detail the scorecard does not clarify: some reports describe Pakistan as finalists, which plausibly means they had already qualified before this match and treated it as a squad audit. On the other side, Sri Lanka's five-bowler split delivered seven wickets to pace — Madushanka five, Fernando one, Malinga one — and three to spin, Arachchige two and Wellalage one.

Core: what 5/34 actually means, and the 15-run stand

Dilshan Madushanka's numbers are clean: 8.3 overs, 34 runs, five wickets, 4.00 economy, a wicket every 10.2 balls. Thirteen years of watching from the boundary edge has taught me that the value of a five-for sits in the phases it arrives in. Here the wickets came in the fourth over (Fakhar Zaman), then the third, seventh, ninth and tenth. New ball, middle overs, tail — all three. A five-for built purely on tail-end wickets carries no predictive weight; this one does. The economy backs it up: 34 runs in 8.3 overs is excellent in a low-scoring ODI.

The figure that points at selection is the biggest stand of the innings: 15 runs. The Salman Ali Agha–Babar Azam partnership, presented as the stabilising passage, did not last four overs in ODI terms. Babar made 29 off 33 at a strike rate of 87.9, the fastest in the top order, but 20 of those 29 came in fours — 69 percent. He fell at 61/5 in 13.1 overs, and with him went the innings' only structurally sound contributor. Hasan Nawaz, at the other end of the ledger, lasted 31 balls for 17 at 54.8 — the longest stay and the lowest return. The anchor role never converted survival into tempo.

Nine fours and three sixes produced 54 boundary runs, roughly 53 percent of the ~101 runs from the listed batters. More than half a total coming in boundaries at 4.31 an over is a strike-rotation deficit dressed up as a scorecard. And the manner mattered: the wickets were scattered from the fourth over to the 25th, one roughly every two and a half overs. This was not one unplayable spell. It was a technical and decision-making failure against sustained pressure, and the boundary dependency and the struggle against spin are two halves of the same problem — a line-up waiting for the big shot instead of working the ball into gaps.

Contrarian: the conclusions forming are larger than the scorecard

Two stories are already hardening. One: Pakistan's batting is broken. Two: Madushanka is an elite quick. Both are possible; neither is established by one innings. I learned to keep the beat by noticing who saves whom a seat in the press box, and here the answer sits in the team sheet. Maaz Sadaqat, Saad Baig, Arafat Minhas and Hasan Nawaz are at least four names in this XI that read as developmental profiles. A five-for against a rotated batting order and a five-for against a full-strength top six are not the same artifact — the discount has to be applied.

The 25.3-over termination also means Madushanka consumed 86 percent of a ten-over allocation inside one compressed block. Whether he carries a full 50-over workload is unevidenced here. Likewise, Fakhar Zaman being out of form is an assertion, not a finding: 13 balls settle nothing, and the source supplies no rolling-window data. Shadab Khan made 2 off 5 days after a maiden ODI century against England — variance, not trend. And the largest absence is the chase result. If Pakistan defended 110, the entire frame flips from batting collapse to a bowling rescue.

Takeaway: the next team sheet is the real story

The noise says Fakhar is out of form and Pakistan's batting is finished. The signal is whether the same four young batters walk out for the next ODI. If they do, this is settled policy and 110 is its price. If they do not, it was an accident and no conclusion is owed. When the whistle goes, I look for the person still standing in the same spot — in this match that person is the selector, not the bowler.