Pakistan's 110 and Sri Lanka's 18.1 overs: what the Lahore scoreboard did not say

Pakistan's innings in Lahore's Gaddafi Stadium ended at 110 in 25.3 overs; thirty-four overs went unused. On that same pitch, earlier in this tournament, a target of 430 was successfully chased — the report calls it the second-highest successful chase in ODI history. That single comparison flips the entire story of this match. A score of 110 does not mean a fast, seaming, conspiratorial pitch. It means a batting unit dismantled itself in one afternoon. Sri Lanka made 111 in 18.1 overs, left 191 balls unused, and finished at a run rate of 6.11. Forty-five minutes later the same pitch looked ordinary. Live xG taught me to read the second screen and the room together. Here the room was shouting that Pakistan's batting was finished; the scoreboard was saying something else — that this match had already been decided before it began.

This three-nation tournament runs on a double round-robin format followed by a final. Pakistan had already qualified with three wins. Which is to say the Lahore fixture was hollow for the host side in terms of consequence, and it came only two days after they had beaten England by one wicket. Being put in to bat is part of the explanation, not the whole of it. In a match where nothing is at stake, selection, rest and intensity all shift — and all three leave marks on a scorecard.

England's story had been written before this match. The report's headline makes Sri Lanka the executioner of England's hopes. Technically correct — after this result England were mathematically out and their last league fixture became a formality. Causally, incomplete. England lost two matches in this tournament from winning positions: they conceded a 430 chase to Sri Lanka, and they let a 242 chase slip by one wicket to Pakistan. England's elimination is the product of the same mistake repeated across two separate matches.

Madushanka's spell and Pakistan's broken spine

Dilshan Madushanka's 5/34 is the most concrete and most transferable data point in this match. The report says he removed Fakhar Zaman in the fourth over — the out-of-form opener could manage only five. That is the wicket that cut Pakistan's innings off before the fifty-over structure could form; by the eighth or tenth over the result was settled. His previous best was 5/80, against India at Mumbai's Wankhede in the 2026 World Cup. Five wickets while conceding 80 tells you he is an attacking wicket-taker, not an economical bowler. In a 110-run match his economy figure will look better than his true level — the one thing that could turn this five-for into a misunderstanding.

Pakistan's scorecard is a report in itself. Top score 29 (Babar Azam), next best 17 (Hasan Nawaz). Fakhar Zaman 5, Saad Baig 5, Salman Agha 9. No partnership reached even thirty. When your highest score in an innings that dissolves inside 26 overs is 29, the problem is not one brilliant delivery but the structure of the entire batting chain. Babar was LBW to Eshan Malinga — the ball coming in towards the stumps, early in the innings, the same old crack. One dismissal does not make a theory; it does point a finger at that crack. At this same ground in 2026, Pakistan collapsed for 75 against Sri Lanka, which the report calls their second-lowest home ODI total. Same ground, same opponent, seventeen years apart, the same falling away — call it coincidence if you like, but call it a pattern and you need more evidence.

Sahan Arachchige's 2/24 reads as a support spell — in a match where the opposition had already collapsed, economy is easy for a spinner. His bowling type is not stated in the report, so do not push this past 'effective support spell'. Shaheen Shah Afridi made 15, took a wicket, and fronted the team's post-match message that they will return in the final and bat better. The message is fine. The real question is whether the top order changes — and the report says nothing about captaincy or selection.

Chasing 111: 191 balls left, few answers found

Kamindu Mendis finished 62 not out off 60 balls, a strike rate of 103.3. Per the report he reached his fifty with a six off Shaheen Shah Afridi — his fifth ODI half-century. Eight fours and two sixes means 44 runs in boundaries, 71 per cent of his total. The strokemaker's method is clear. Pavan Rathnayake stayed with him on 23.

The question is what we learn from the innings. A target of 111 in 18 overs with wickets in hand is a see-it-home innings, not an evaluation innings. The real signal is that by his fifth ODI fifty he still has no ODI century to his name. That is an unconverted profile — the talent shows, the long innings does not. Read it as a metric to track, not a criticism; the next ten innings will answer it.

The real story belongs to England, not Sri Lanka

One thing needs saying plainly. What Sri Lanka won is a genuine win — eight wickets, 191 balls spare, no doubt about it. But England's exit was not caused by this Sri Lanka win; it was caused by England's own two collapses. Conceding a 430 chase and losing a 242 chase by one wicket are not batting failures but middle-overs and death-overs bowling failures. England scored enough to win both matches and lost both. That is a repeatable failure signature, not an accident — and it cannot be diagnosed in their last league game, because that game is now meaningless. A good performance in an empty contest is not proof of recovery.

Second, do not turn 110 into a trend. Pakistan had already qualified, had played two days earlier, and had nothing riding on this match. Team changes, rest and a dip in intensity are all plausible. The report does not confirm any change to Pakistan's XI, and that is the single biggest missing piece of information in the whole story. A number that arrives without an explanation is a question, not a conclusion. Treating 110 as the yardstick for the final repeats the same error that ignores the same team's 242 chase two days earlier.

Third, honesty. This report is single-sourced, with no named agency, journalist or scorecard link. From Madushanka's 5/34 to the 430 chase, every figure is pending verification. In a Chennai startup I learned that empty tables make loud enemies — and the database started empty, with the first real finding arriving as a fight. A model is only as honest as the questions it refuses. Here the model says: one innings does not establish a batting decline, even if that innings stopped at 110.

What to watch next

Sunday's final is now a pure narrative-volatility event. If Pakistan win, the 110 becomes an anomaly; if they lose, the same 110 becomes proof of structural decline. One number supports both stories, which is exactly why it should not be used as evidence for either. What to watch is this: how many wickets Pakistan lose in the first ten overs of the final. Two or more, and the top-order vulnerability against the new ball is established. And for Sri Lanka: whether Madushanka bowls a full quota in a dead rubber — that would be a statement about workload, not selection.