110 All Out in 25.3 Overs in Lahore: A Deep Reading of Pakistan's Batting Collapse
প্রশ্ন: পাকিস্তান কেন ২৫.৩ ওভারে ১১০ রানে অলআউট হলো? উত্তর: মূল কারণ পাওয়ারপ্লেতে তিন উইকেটের ধস, স্ট্রাইক রোটেশনের অভাব, পাতলা টপ সিক্স ও লম্বা লেজ, এবং শ্রীলঙ্কার দুই ধাপের Bowling পরিকল্পনা—নতুন বলে সিম ও মধ্য ওভারে স্পিন। ১১০ রান গাদ্দাফি Stadiumের দ্বিতীয় সর্বনিম্ন ওয়ানডে স্কোর এবং প্রথম Inningsে সর্বনিম্ন; এটি পিচের নয়, বেসলাইনের সঙ্গে পার্থক্যের সংকেত। চেজের ফল, টস, পিচ রিপোর্ট ও ডিসমিসালের ধরন যাচাইয়ের অপেক্ষায়।
In the fifth ODI tri-series match at Gaddafi Stadium, Lahore, Pakistan were bowled out for 110 in only 25.3 overs. The supplied analytical points do not name a source, give a specific date, confirm the toss winner, provide a pitch report, mention DLS conditions, or state the chase result. This report therefore focuses on the innings total, overs faced, wicket distribution, individual scores and historical context, and clearly marks missing data as awaiting verification. The central cricketing fact is that a 50-over innings ended in 25.3 overs, meaning Pakistan never reached the two-new-ball, middle-overs spin-control or death-overs phases. The competitive phase of the match was effectively decided inside the first 14 overs of the first innings.
The powerplay collapse was severe. Pakistan lost three wickets inside seven overs for only 18 runs: Fakhar Zaman 5 off 13, Maaz 8 off 11 and Saad 5 off 8. At 61-5 after 13.1 overs the innings was structurally broken, and the last five wickets added only 49 runs in 12.2 overs, about 3.97 runs per over. A total of 110 off 153 balls is a team strike rate of roughly 71.9, or about 4.31 runs per over. Even a collapse running at 5 runs per over would have produced around 128, so the low total reflects both wickets and an inability to rotate strike.
The venue context makes the failure more serious. The 110 is the second-lowest ODI total at Gaddafi Stadium, behind only 75 in 2026. But that 75 came in the second innings, in chase conditions; a first-innings 110 on a home ground is the more damning number. The ground's historical scoring baseline is far above 110, so this is a performance outlier rather than a pitch-driven freak. For Pakistan this is a home failure, which removes the usual mitigating factors of unfamiliar conditions and foreign bounce.
Babar Azam was the top scorer with 29 off 33, a strike rate of about 87.9. His 29 runs were 26.4 percent of the team total, and five fours meant about 69 percent of his runs came in boundaries. Elite ODI anchors usually take 45 to 60 percent of their runs in boundaries. Babar was the only batter who survived the new-ball phase with some fluency, but his innings did not shape the team total. The high boundary dependence suggests burst scoring and poor strike rotation while wickets fell at the other end.
The top-order failure was collective. After Fakhar, Maaz and Saad, Hasan Nawaz made 17 off 31, the second-best score. Five of the top six scored under 10. Three separate failures in the same phase point to preparation, role clarity and exposure to the moving ball rather than one star's failure. Pakistan's XI appears to have been rotated or partially second-string: several low-profile top-order names and a long tail, with captain Shaheen Afridi batting at No. 9 and Haris Rauf at No. 10. Rotation may explain selection, but it does not excuse 110.
Shadab Khan's 2 off 5 should not be read as a form collapse. He had scored his maiden ODI century against England in the previous match; a 2 in the next innings is small-sample variance. The meaningful point is that Pakistan's No. 6 or 7 all-rounder is being asked to rescue innings rather than finish them.
Dilshan Madushanka produced the standout individual performance: 5/34 in 8.3 overs, an economy of about 4.0 and a bowling strike rate of about 10.2 balls per wicket. He bowled 8.3 of the team's 25.3 overs, about 33 percent, and took 5 of 10 wickets, 50 percent. Left-arm pace with new-ball wickets and a sub-4.5 economy is a scarce profile, but this is one match; without career averages, condition splits and dismissal modes, it cannot establish a career level.
Sri Lanka's bowling unit showed multi-phase structure. Madushanka took 5, Asitha Fernando 1 and Eshan Malinga 1, so all three seamers took wickets. Sahan Arachchige took 2 and Wellalage 1, so spin took 3 of 10 wickets inside a 25-over innings. Wicket-sharing across five bowlers is a depth marker. The likely plan was seam with the new ball and spin control in the middle overs, though dismissal modes are not supplied.
Historically, Pakistan's vulnerability against Sri Lanka is repeated and documented: 75 in 2026, 102 in 2026 and 110 in this match, three sub-110 first-innings totals against the same opponent. That is a matchup signal, not a coincidence. Commercially, an innings ending in the 26th over removes roughly half a broadcast property's inventory and the death-overs advertising premium. A host nation being dismissed for 110 in match five of a non-marquee ODI tri-series compounds the format's structural fragility. Madushanka's 5/34 is the most auction-relevant performance in the article; Shadab's previous century would have been the series' commercial highlight, but his 2 off 5 made it fleeting.
Data gaps remain critical: no named source or date, no pitch report, no toss confirmation, no DLS reference, no dismissal modes, no chase result and no career splits. Therefore this innings cannot be used to prove a long-term decline, and Madushanka's haul cannot establish a career level. One conclusion is high-confidence: the match was effectively decided inside the first 14 overs, and 110 is a par-versus-baseline failure, not a par-versus-pitch story. Without re-examining batting preparation, top-order roles and new-ball technique, repetition is likely. For Sri Lanka, the match is evidence of bowling depth and a two-phase plan; for Pakistan, it is a harsh mirror of structural weakness at home.


Related Players
Recommended
Asia's Franchise Auctions: The Market Does Not Pay for Talent, It Pays for Repeatable Evidence2026-10-03
Who Is the Real King of Sixes in T20? How Strong Is Bangladesh's Hand?2026-10-19
What Is Settled Before the Ball Moves: Asian Cricket's Invisible Blueprint in the Shadow of the Asia Cup2026-10-03
Haris Rauf and BBL 16: One Rumour, One Calendar, and Cricket's Shifting Map2026-10-09
In Bengaluru Decider, India's Real Question Is Bowling Balance, Not Vaibhav2026-10-18
Shreyas Iyer's Cautionary Note: The Philosophy of Waiting for Vaibhav Sooryavanshi2026-10-22
Recommended
The Spin Ledger on Lucknow's Slow Pitch: A Tactical Preview of India vs West Indies 1st T20I2026-10-06
Litton Das's World Record: A Statistical Curiosity on Abu Dhabi's Slow Pitch2026-10-14
Drones to Catch Umpiring 'Theft': The Unasked Questions Behind BCB's Tech Purchase2026-10-22
The Plan to Keep It Tight: Shai Hope, Arshdeep Singh, and Digging for the Roots of India's Bowling Thought2026-10-12
Green Dashboard, Empty Payload: Why a Null Result Is Worth More Than a Fabricated Cricket Analysis2026-10-20
