Pakistan All Out for 110: The 24.3 Overs Nobody Batted Out

Gaddafi Stadium, Lahore — the fifth match of a tri-nation series. Pakistan lost the toss, were inserted, and were bowled out for 110 in 25.3 overs. The scoreboard shouted 110. My notebook underlined 24.3 — the overs no Pakistan batsman ever faced.

A fifty-over match finishing in the 26th over is a statement in itself. This is not the story of a bad ten-over patch. In a bad ten-over patch you still reach the 48th over and get to 240. Here the side went back before using half its allocation. When a team is bowled out before its halfway quota, the question is not how many runs it made; the question is how many balls it left behind.

And the second number that stopped me: Dilshan Madushanka's spell is recorded at 8.3 overs. That single figure establishes the format. No bowler may bowl more than four overs in a T20, and four in The Hundred. An 8.3-over spell exists only in a fifty-over game or a Test, and with a single-innings scoreline, this is an ODI. I am spelling that out because the most common failure in our match reporting is conclusion-drawing on an unverified format — we reach for the nearest framework rather than the correct one.

The context, as far as it exists

Pakistan were the hosts. Gaddafi Stadium has been rebuilt and re-launched as a showcase venue, and historically it has been a batting ground where 300-plus is a par first-innings score: short boundaries, good surface, evening dew. 110 all out at that venue is an anomaly, and anomalies are where the real questions hide.

Being the fifth match matters too. A three-team round-robin means six league games and a final, so match five carries direct table consequences. This defeat costs more than one result.

Now the honest part. The material I am working from carries no source attribution for a single fact, no named outlet, and no record of the second innings. The numbers that do exist — 110 in 25.3, Madushanka's 5/34 — are internally consistent, so fabrication is unlikely. But every conclusion currently rests on one innings of one match. I do not chase predictions; I collect the small signals that make them feel obvious afterwards. And a collector has to admit how light the bag is. Because the chase and the result are not in front of me, I will not write that Sri Lanka crushed anything. My analysis stops at the first innings — and the first innings is already full.

The core: this is a wickets story, not a slow-pitch story

First, the dull, conventional explanation, in full. Lahore was slow, the ball was holding, the batsmen never found timing. It is a comfortable explanation because nobody is at fault. I weigh it, then say why it fails.

On a genuinely difficult surface sides survive longer and score slower. They do not fold in the 26th over. 153 balls for ten wickets means the average partnership was about 15 balls — no pair survived even three overs on average. That is not a bowling side squeezing the game; that is a batting unit being beaten technically. On a slow pitch you score slowly. You do not get dismissed at that rate.

The run rate reinforces it. 110 in 25.5 overs is 4.31 an over. Contemporary ODI par at a Pakistani venue sits somewhere between 5.5 and 6. Extrapolated at the same rate across fifty overs, Pakistan reach roughly 215 — sub-par on its own. So the real cost is not "110"; it is "110 with the innings truncated." Runs and balls are two separate assets, and Pakistan lost both in the same morning.

Madushanka's 8.3 overs: the one figure that explains the innings

5/34 in 8.3 overs. Economy 4.00, strike rate 10.2 balls per wicket. Read those together. ODI par economy is around 5.5 and par strike rate around 30 balls per wicket. Here a bowler took wickets and conceded nothing — the signature of a man who was never allowed to be played out. A bowler taking five at an economy of four was never a phase of the game; he was the question the whole innings was answering.

And the mechanism is visible from the ground. A left-arm seamer against a right-hand-heavy top order, with a hard ball in the early and middle overs. An 8.3-over spell does not fit inside a single new-ball burst, so he almost certainly bowled two: the opening burst, then a return to break whichever partnership had formed between the third and fourth wickets. I once set a field for Anjum Chopra and the knee wrote a different ending; that day taught me that a plan is clearest on paper and least guaranteed on grass. Sri Lanka's plan was clear enough that it never needed rewriting.

One caution. The modes of dismissal are not recorded — how many LBW, how many caught, how many bowled. Without that list, saying the left-arm angle broke Pakistan is an attractive inference, not a demonstrated fact. I put it in the inference column, not the conclusion column.

Babar's 29: the most damning number is the top score, not the total

Babar Azam came in at three, tried to hold on, got a start, and could not convert. 29 — 26.4 percent of 110. Read superficially, that looks like resistance. Read properly, it inverts. When a team's top score is 29, the failure is distributed: nobody can be blamed and nobody can be credited either. A batsman who makes 29 at 30 for 4 did not save the innings; he simply waited longest before it ended.

And a real gap: his balls faced are missing. Without them, any claim that he anchored too slowly or batted well is groundless. That matters especially because the entire public argument about Babar in white-ball cricket has been a strike-rate argument. The argument is about balls faced; the balls faced are absent. Forming an opinion on a missing number is not analysis, it is habit.

Hasan Nawaz's 54.8 strike rate: a tactical artefact, not a technical flaw

17 off 31. Modern ODI numbers six and seven run at 85 to 100, so the raw figure looks ugly. Put it in context. In a collapse, occupying the crease has genuine value. His actual error was the shot he lost patience for, caught trying to force the pace. By the 20th to 25th over at 54.8, the required rate was already climbing, so the intent was defensible in isolation. The real failure was earlier, at 20 for 2 or 30 for 3, when nobody rotated strike. In a crisis the crime is rarely the last shot; the crime is the fifty dot balls that manufactured the crisis.

Shaheen's 15 off 13: a diagnostic, not resistance

Shaheen Afridi made 15 off 13 at 115.4. Several reports will file that under "helped Pakistan reach a hundred." I do not buy it. When a team's most fluent scorer is its number nine, that is not a compliment to the batting; it is an indictment of the top order. Tail-end runs fill the scoreboard and cover the problem. Pakistan did not reach 110 because Shaheen batted fast; they reached 110 because Shaheen had to bat.

Host status cuts against the excuse

Here is the inconvenient fact our reporting reflex ignores. Pakistan were at home. Struggling with unfamiliar conditions is normally the visiting side's problem. Pakistan collapsing at home, in front of their own crowd, on their own square, dismantles the first excuse available: that the pitch was unplayable. And if the surface really was so loaded, why did Sri Lanka choose to field on winning the toss? Sides that fear a pitch bat. Sri Lanka bowled — which tells you they expected early help, and that their read was right.

The contrarian angle: the toss is the easiest and worst alibi

Pakistan lost the toss and were inserted. Facing morning moisture and a hard new ball genuinely is a disadvantage. All true. But a toss disadvantage costs you two or three wickets, not ten. Losing ten for 110 requires six or seven batsmen to make errors that belong to technique and decision-making, not to a coin. I am tired of how much room we hand to luck in every defeat, until there is no room left for technique.

Second counter-angle, turned on my own thesis. This innings is not proof of a Pakistani batting decline. One innings, one day, one surface. Establishing a trend requires the surrounding three to five innings, and that queue is not in front of me. Anyone announcing a structural crisis off this 110 is repeating the error made after the 2026 T20 World Cup and forgotten within six months.

Third, and least comfortable. There is no pitch report in my material. I cannot say the pitch was bad and I cannot say it was fine. But if the surface genuinely offered that much to bowlers, a question travels to the host board: why prepare a surface on which your own side cannot last twenty overs? What instructions the curator received is unrecorded. That is a question, not a finding — and good analysis is mostly the discipline of keeping questions from hardening into findings.

One professional caveat. The name "Saif Beg" appearing in the squad list is very likely a transliteration of another Pakistan player. Verify it before drawing any player-level conclusion. Being the only woman on the Hindi panel taught me to read the room before the replay, and the room taught me this: someone careless with a spelling is often careless with a statistic.

Takeaway: watch three things next match, not three excuses

First, Pakistan's strike rotation in the first ten overs. If they are 20 for 2 again with a pile of dots between overs twenty and thirty, this was a habit, not an accident. Second, whether the opening pair changes. An opening pair where neither man reaches double figures is a selection question, not a talent question. Third, Madushanka's next spell. If he again takes wickets inside his first three overs with the new ball, we will know this was a structure, not a day.

And until those three answers arrive, one question stays with me. 153 balls. That is all Pakistan faced, and no pair averaged beyond three overs. When a side has sixty overs available and comes back in twenty-five, was that a bad pitch — or a bad morning we would rather call a bad pitch?