110 in 25.3 Overs: The Real Defeat Inside Pakistan’s Batting Collapse at Lahore

The Number on the Board

On a Mumbai evening, the Lahore feed was on my screen. The scoreboard read 110/10 in 25.3 overs. My mind went back to Wankhede in 2026, when Amol Muzumdar batted two days for 260 in the Ranji final and I wrote 900 words from a dressing-room corridor that smelled of linseed oil. My editor cut it to 300 and kept one line: cricket is the only art form where the audience is allowed to interrupt. The Lahore feed gave me that permission again. The number stayed on the board; the smell of linseed oil stayed with me.

At Gaddafi Stadium, Pakistan lost the toss and batted first. It was the fifth match of a tri-nation ODI series. Pakistan were the hosts. Sri Lanka chose to field. The innings ended at 25.3 overs, leaving 24.3 overs unused. That is the number that falls out of the headline. Reading 110 is easy. Reading 24.3 overs is harder.

The Lahore Context

Before judging the innings, the format has to be settled. The available match sheet records Dilshan Madushanka’s spell as 8.3 overs. A bowler is capped at four overs in T20. An 8.3-over spell is possible only in a 50-over match or a Test. A single-innings scoreline, a tri-nation series and limited-overs framing make this an ODI. That is a rules-based inference, not a guess.

The record also has no date, no publication outlet and no second-innings detail. We do not know how Sri Lanka chased, whether they won comfortably or stumbled. So this piece stays with Pakistan’s first innings. I spent three seasons learning the corridors before I understood the lights. In those corridors, the loudest thing is not the scoreboard; it is the silence around it.

Babar Azam top-scored with 29. Hasan Nawaz made 17 off 31. Shaheen Afridi made 15 off 13. Dilshan Madushanka took 5/34 in 8.3 overs. Both openers failed to reach double digits. No partnership of substance formed. The innings moved through regular wickets.

The Score Is 110; the Structure Is 25.3 Overs

Pakistan faced 153 balls and lost ten wickets. The average partnership was 15.3 balls. No pair survived even three overs on average. The run rate was 4.31. At a Lahore venue, that is roughly 1.2 to 1.7 runs per over below contemporary ODI par. Extrapolated over 50 overs at the same rate, Pakistan would have reached about 215. The real cost is not 110. It is 110 with the innings truncated.

On a slow pitch, sides usually survive longer and score slower. Here the innings shrank because wickets fell. The match sheet does not tell us whether the ball was slow or quick. The wicket pattern tells us the batting unit was beaten technically. Being bowled out inside 26 overs means the bowlers were not merely containing; they were taking wickets. A difficult surface usually produces a lower run rate with more overs consumed. This produced the opposite.

A Top Score of 29

Babar made 29, which is 26.4 percent of 110. A No. 3 batter on a good day is expected to make 35 to 45. A 29 means he started, survived, resisted, and failed to convert. The record does not give his balls faced or strike rate. So no claim that he batted too slowly or too quickly can be supported. The public debate around Babar’s white-ball strike rate cannot be settled by this innings.

When a team’s top score is 29, the failure is distributed. Blaming one batter is easy and useless. Babar offered resistance; resistance is not vindication. A top-order batter making 29 cannot rescue an innings that collapses inside 26 overs. This is not his private defeat. It is the defeat of a structure in which no batter from the top seven could produce a substantial innings.

Openers Under Ten

Neither opener reached double digits. That detail makes Babar’s 29 harder to read. At 20/2 or 30/3, the No. 3 batter has to stabilise from the first ball. Babar had to secure the innings before scoring. When the top order falls cheaply, the middle order stops rotating strike and starts surviving. The run rate dips, and the bowling side gets more time to attack.

Opening fragility is not a new theme in Pakistan’s white-ball batting. One innings cannot prove a trend. What it can show is that on this day, the opening failure compressed the entire structure around Babar.

Hasan Nawaz’s 54.8

Hasan Nawaz made 17 off 31, a strike rate of 54.8. A modern ODI No. 6 or 7 is expected to score at 85 to 100. The number is low, but context matters. The innings was collapsing. Occupying the crease had value. His error was not the slow rate; it was losing patience and attempting a big shot. He was caught.

In the 20th to 25th over, with the required rate climbing, the shot was defensible in isolation. The real failure came earlier, at 20/2 or 30/3, when nobody rotated strike. Hasan bought time. The team did not use it. This is less a story of technical accident than of collective decision-making.

Shaheen’s 15 off 13

Shaheen made 15 off 13, a strike rate of 115.4. For a fast bowler, that is a useful contribution. It is not a sign that Pakistan’s batting was healthy. When a frontline fast bowler batting at No. 9 or 10 is the second-most fluent scorer, the top seven were comprehensively outplayed. Tail-end runs can reveal depth. Here they exposed the lack of it above.

Shaheen helped Pakistan reach 100. Media framing can call that resistance. I read it as a diagnostic. When the tail looks more comfortable than the top order, the problem is in the first seven batters.

Madushanka’s 8.3-4-34-5

Dilshan Madushanka took 5/34 in 8.3 overs. Economy: 4.00. Strike rate: 10.2 balls per wicket. ODI par is roughly 5.5 an over and about 30 balls per wicket. This spell was far ahead of that. He delivered 33 percent of the innings’ overs. Taking wickets at 4.00 an over means no batter was allowed to play him out.

The left-arm angle against a right-hand-heavy Pakistan top order is a familiar challenge. The spell likely spanned the new ball and early middle overs. An 8.3-over spell is longer than one burst, so he probably returned to break the Hasan Nawaz stand. The dismissal modes are not recorded, so the mechanism stays uncertain. What is clear is that Sri Lanka’s plan was attacking, not merely restraining.

The Lahore Anomaly

Gaddafi Stadium is conventionally a batting-friendly venue. A 300-plus first-innings score is normal. A 110 all out there is not impossible, but it is anomalous. The cause could be residual moisture, early seam movement or simply poor batting. The match sheet has no pitch report and no weather detail, so these causes cannot be separated.

A host side being bowled out for 110 at home weakens the conditions excuse. Visiting teams are the ones who normally struggle with unfamiliar surfaces. Pakistan were at home. If the pitch was genuinely unplayable, the question of why the host board prepared it becomes legitimate. That is a question, not a finding.

The Tri-Series, the Board’s Pitch, the Brand Cost

Tri-nation ODI series sit at the edge of the calendar. The IPL window, FTP bilateral commitments and T20 leagues squeeze their space. A fifth match implies table pressure, not a dead rubber. A 25.3-over innings in that setting carries a psychological cost beyond one defeat.

Gaddafi Stadium is a recently redeveloped showcase venue. A sub-120 home total damages the product being sold to broadcasters and sponsors. The match was over as a contest inside half an innings.

The host board controls pitch preparation. No pitch report is available, so no claim that the surface was poor can be supported. But it is fair to ask why a host board produced a surface on which its own side was bowled out for 110. Between April and the verdict, the winter taught me how institutions breathe. Their breath shows up in the curator’s notebook, not on the scoreboard.

The record contains no DRS controversy, no rain, no DLS. The innings ended by dismissal, not interruption. On the available information, this is a clean cricketing outcome. If Sri Lanka chased, the details are absent. So no claim about how they dominated will appear here.

The Easy Story and Its Hidden Bill

The easy story is that the pitch was slow, the toss mattered and Pakistan had one bad day. That story is comfortable. The toss does not take ten wickets. Home conditions are not unfamiliar. One bad day does not explain ten wickets in 25.3 overs.

The second easy story is to turn Babar’s 29 into proof of resistance. It was resistance, not proof. If Pakistan’s next three to five innings produce 250-plus scores and this stands as a lone outlier, my structural reading is wrong. I pre-register that falsifier. One innings cannot establish a batting decline. But an average partnership of 15.3 balls does show that on this day the top order had no plan against the new ball.

The third easy story is that this was just another Pakistan defeat. For me it is a freeze-frame of the moment when the scoreboard, the commentary and the selection language all change. Leaving 24.3 overs unused means the team played a 25-over game inside a 50-over format. When the top order falls cheaply, the middle order defends, strike rotation stops and the bowlers get time to attack.

The Number Stayed on the Board

The result is unavailable. The second innings is unavailable. So I will not write a verdict on Sri Lanka’s win or Pakistan’s defeat. I will leave the question the Lahore scoreboard asked: who consumed the 24.3 overs? Will the next morning bring mourning for 110, or an audit of the first 15 overs? A stadium can hold a record and still hide the people who made it possible. The curator’s notebook, the dressing-room silence and the 24.3 unused overs will meet again. The question is whether Pakistan will have changed the language of their batting by then, or merely called 110 a bad day and moved on.