Pakistan 110 All Out in Lahore: The Selection Story Behind Madushanka's 5/34

The number that appeared on the Gaddafi Stadium scoreboard after the last ball of the 25th over — 110 — read less like a total and more like an absence. A fifty-over match ended in 25.3 overs. That leaves 147 balls that were never bowled, and a home side that never came back out to face them.

Start with a detail no scorecard headline carries. The six that took Pakistan past one hundred was struck by Shaheen Afridi — a fast bowler coming in from the lower order. In an innings where the top order could not read the ball, the highest strike rate (115.4) belonged to a number eight or nine. That is not an embarrassment anecdote. It is the clearest clue to the architecture of the innings.

That this happened in Lahore is itself the event. This is a ground where two hundred is ordinary, where the ball comes on and spinners are used for control. A total of 110 there is an outlier — and an outlier has to be read like a team sheet, not a headline.

The context the report omitted

Match five of a tri-series, Pakistan at home, batting first after winning the toss. The source report calls Pakistan "finalists," a word that carries a probability — the side may already have qualified, which would change the match's priority. The other reading cannot be excluded either: "finalists" could refer to a previous edition. Both readings land in the same place. This XI contained four names that read as emerging: Maaz Sadaqat, Saad Baig, Arafat Minhas and Hasan Nawaz. Alongside them were Babar Azam, Fakhar Zaman, Salman Ali Agha, Shadab Khan, Shaheen Afridi, Haris and Naseem Shah. This was neither a full experiment nor a settled side; it was the transition state where the senior spine stands and the tier beneath it is tested in a single afternoon.

ODI batting has its own clock. A platform is built between overs thirty and forty, and the last ten overs are run from that platform. Pakistan never reached the platform. By 6.2 overs they were 23 for 2 at 3.60 an over; the middle block produced 68 for 5; the tail added 19 for 3. No acceleration phase existed. And the report records no rain and no Duckworth-Lewis-Stern revision. This was a batting collapse, not a weather event.

Honesty is required here. I do not have the toss, the pitch report, or — most importantly — the result of the chase. The report stops at the innings break. That means nobody is in a position to say Sri Lanka won this match, because the defence of 110 is still unwritten. I am writing from Mumbai, not from the commentary box in Lahore; what I have is a syndicated wire report and its dense ball-by-ball skeleton.

Thirteen years ago, on a digital desk in Mumbai, I was asked to file 250-word agency-fed match reports, and for four years I was told that tactics were "for the boys" in press boxes where I was usually the only woman in the room. The tactics were never for the boys; they were for anyone who stayed awake.

A drip-collapse, not a clatter

Read the scorecard in sequence. The first wicket in the fourth over, the second around the sixth or seventh, the third in the thirteenth, a fourth shortly after, and then a steady run from the twenty-first onward. Across the innings, a wicket fell roughly every two and a half overs. Nowhere did three wickets fall in one over. This was not one unplayable spell; it was decision-making breaking under sustained pressure. When a bowler takes three in an over, the story belongs to him. When wickets fall every 2.5 overs, the story belongs to the batting plan, the partnerships and the captaincy.

Madushanka: a phase-agnostic five-for

The figures record the performance: 5 for 34 in 8.3 overs, an economy of 4.00, a bowling strike rate of roughly 10.2 balls per wicket, an innings average of 6.80. In a low-scoring ODI, an economy of four is excellent.

The real signal, though, is in the sequence. The first wicket came in the fourth over with the new ball. The third and seventh came in the middle overs, when batters are set. The ninth and tenth cleaned up the tail. Five wickets arrived in four different circumstances, and that is what makes this five-for the most transferable signal in the dataset. Had all five come at the tail, the story would be different.

The discount matters just as much. At least four batters in this Pakistan XI carry developmental profiles. Five wickets against a full-strength top six and five against four emerging batters are not the same thing, and that gap must be tagged onto every downstream use of these figures. One more detail: 8.3 overs is 86 per cent of a full ten-over allocation, delivered in a single compressed block. There is no evidence here of Madushanka in a second or third spell under fatigue — his ceiling across a full 50-over workload remains unmeasured.

A technical point the report does not raise: it was the left-arm angle that kept pressing the right-handed top order. Fakhar Zaman and Saad Baig both tangled with it. Left-arm pace against right-handers is a documented structural pressure point in subcontinental cricket, and the report passes over it as "impressive bowling."

The myth of the 15-run stand

There is a gap between the report's language and the numbers it supplies. The Salman Ali Agha–Babar Azam partnership is described as the innings' stabilising passage. Its value: 15 runs. In ODI terms, that is under four overs of survival. Calling it a platform is generosity of language, not an achievement of data. Pakistan reached 91 for 7, and the last three wickets added 19. Without that tail, the total sits in the nineties and the depth of the failure looks materially worse. The tail covered part of the collapse, which is why 110 sounds less frightening than 91.

Boundary dependency is the second tell. The innings recorded nine fours and three sixes — 54 runs straight from the boundary. The listed batters account for roughly 101 runs, so about 53 per cent of the total came in boundaries. A side scoring at 4.31 an over with more than half its runs from fours and sixes is carrying an enormous dot-ball and strike-rotation deficit. That is the signature of a batting group that cannot work the ball into gaps.

Babar Azam is the most contradictory figure in the innings. 29 off 33 balls, a strike rate of 87.9 — technically the best top-order return. But 20 of those 29 runs, 69 per cent, came in fours. A batter who scores only in boundaries or not at all failed to rotate strike against the middle-overs plan; that is the read the report does not make. His dismissal at 61 for 5 in 13.1 overs was the innings' most consequential moment in process terms. No batter after him reached 20.

Hasan Nawaz is the inverse case. 17 off 31 at a strike rate of 54.8 — the longest stay in the innings and the lowest return. That is the anchor's trap: surviving is easy, converting survival into tempo is not. Arafat Minhas (10 off 18) neither survived nor accelerated.

Reading Shadab Khan's 2 off 5 as a conclusion would be a textbook small-sample error, and the report itself supplies the antidote — it notes his maiden ODI century against England. A batter who faces five balls does not change form; he gets out once.

The report's "out of form" label on Fakhar Zaman reads like a finding but is not one. No rolling-window data accompanies it — no five- or ten-innings average, no strike-rate trend. One 13-ball innings neither establishes nor refutes form. This is authorial judgement, unverified. What the data can say concerns age: an opener born in 2026, powerplay-dependent, past thirty. The decline risk here is structural, not form-based.

The bowling split tells its own story: seven wickets to pace (Madushanka 5, Fernando 1, Malinga 1) and three to spin (Arachchige 2, Wellalage 1). Wellalage is a left-arm spinner, Arachchige an off-spinner who is primarily a batting all-rounder. Sri Lanka used spin for middle-overs control, and that control produced the wickets of Salman and Shadab. It is the oldest pattern in the book: control spin takes the set batter, the new ball takes the uncertain one.

The scoreboard says crisis; the team sheet says choice

This is where the convenient story and the durable story separate. The convenient story is that Pakistan's batting is broken. It has not been disproved, and it has not been proved either. Putting four developmental batters into one ODI XI at home is a strategy with a pre-agreed cost. Lahore is where that cost was paid — this is less a batting failure than a selection bill.

On the other side stands Madushanka, and this is where the market will err fastest. A five-for spread across every phase is genuinely high quality — but it came against an innings with no established anchor beyond Babar. The market will price this five-for above its evidential value, and that gap should be closed over a series, not a week.

The largest gap of all is the result. The chase score, the margin and the conditions are all missing. If Pakistan defended 110 — and this report cannot rule it out — the entire framing inverts from a Sri Lankan bowling masterclass to a Pakistani bowling rescue. Hiding that uncertainty from the reader would be an editorial theft.

And one warning that is rarely written in sports journalism: format bleed. Several players in this XI are T20-primary. Their T20 strike rates cannot be imported here, and this ODI collapse cannot be exported into T20 or Test judgements. One innings, one venue, one rotated XI — any larger conclusion is evidence of our haste, not of the data.

Takeaway

Read Pakistan's next team sheet more carefully than this scoreline. If the same four emerging batters are picked again, it is policy, and Lahore's 110 was its first invoice. If the selectors snap back to seniority, it was an accident, and the team management is saying so itself. Madushanka's next two spells will settle what this five-for is worth — he has not yet carried a ten-over load. The final whistle does not close the story; it opens the door for questions — and here, the innings break has done exactly that.