110 in Lahore: Pakistan's Batting Fault Line Opens Before the Final, England Are Out

The smallest number on the Gaddafi Stadium scorecard is the biggest story — 15. Shaheen Shah Afridi's 15. Pakistan were bowled out for 110 in Lahore, and a fast bowler was walking back with fifteen runs to his name at number eight or nine. That means one thing: the top order had already gone inside the first 12 or 13 overs. The ground that will host the final is the ground where the host side folded for 110. This is also the Lahore where evening dew softens the ball and rewards the chasing side more than the bowling side — and the report carries no toss, no dew, no weather.

The report I received has no economy rates, no balls faced, no net run rate, and no stated format. One line says Sri Lanka "did not lose another wicket" after a fifty-run opening stand, while the same report shows Kusal Mendis dismissed for 8 off 6. The totals add up — 16+8+62+23 is 109, plus two extras is 111 — but the sequence is garbled. The arithmetic holds; the narrative does not. I have a habit of doing sums on the scorecard before reading the headline, and that habit earned its keep here.

In 2026, writing sponsor content in Hyderabad, a brand asked me to frame Sunrisers' 158/6 heroically. I pulled the phase splits, saw only 41 runs in the last five overs, and wrote that the total was 12 short on a flat Rajiv Gandhi deck. The client killed the piece and the contract died with it. The rejected draft went up on my own handle and drew 18,000 reads and 400 arguments. I killed a sponsorship by telling the truth about a 158-view video — and since that day every hot take of mine carries a phase split, a result context, and one number that challenges the headline. This Pakistan-Sri Lanka match is going through that same filter.

The table is talking, and it is not talking about cricket

A tri-series: Pakistan, Sri Lanka, England, hosted in Lahore. The standings read like this — Sri Lanka unbeaten on six points from three, Pakistan top on six points from four, England eliminated on zero from three. The final is Pakistan versus Sri Lanka. England's elimination arithmetic is clean: a side on zero from three cannot reach Sri Lanka's six under any standard points system.

What is not clean is the logic of the team sitting on top. Sri Lanka are second with three wins from three, while Pakistan are first despite a defeat — a defeat to the very side ranked below them. That is only possible with a large net run rate cushion, meaning Pakistan's earlier wins came by wide margins. The report contains not one NRR figure. The other possibility is that the points system itself is different — six points from three matches could be two wins at three points each, or three wins at two points each. Until the system is stated, "Pakistan are top of the table" is not a conclusion. It is an assumption.

This is exactly where the commentary box and the data desk part ways. The box says the hosts are top despite a loss, morale intact. The desk asks: by which system, at what run rate, by how many runs in which match? My politics have always sat with the desk.

England's exit is a fact. "England are in crisis" is an inference, and selling it as a fact is the same old habit I have spent years fighting. Who played in those three defeats, what strength of opposition turned up, what format it was — not one of those details exists in the report. To reach a diagnosis I need scorecards, not the mood of a press conference.

Five wickets do not always mean five wickets

Dilshan Madushanka's five-for is the most valuable data point in this story and the most useless one at the same time. A five-wicket haul tells you wickets fell. It does not tell you how good the bowler was. For a left-arm quick, 5/18 — a tight new-ball spell plus death accuracy — and 5/32 — early breakthroughs then expensive at the end — are two entirely different bowlers. The report gives no overs, no runs conceded, no economy. My verdict on Madushanka is therefore adjourned, and I am not going to pretend otherwise.

Based on my years of watching matches, five wickets in a 110-run game usually comes from something specific: new-ball swing, with batters already feeling the scoreboard. Pakistan's top order manufactured that pressure themselves. If Madushanka took three in his first four overs and the last two came from batters hurrying to score, the five is accurate and the picture is incomplete. The real question for the final is this: when the target is not 111 but 170, what do his overs 15 to 20 cost?

Sri Lanka's bowling strength is not in the one man with five wickets; it is in the distribution. The report indicates Sri Lanka used at least five bowlers — Madushanka's five, two for one bowler, one each for three others. Rotating five bowlers while defending 110 is not easy, and it suggests the captain had options and trusted them. That is precisely what travels into a final: a second route on a day when the strike bowler is off.

Pakistan's 110 is not an accident, it is an architecture

Babar Azam top-scored with 29. After him: 17, 15, 10. Four batters reached double figures; the remaining seven plus extras shared roughly 39 runs. This was not a lower-order collapse. It was a top-order collapse. Note the distinction. If six or seven wickets fall in the last ten overs, the story becomes "runs dried up at the death." Here the story is inverted — Shaheen made 15 because he walked in with only 25 or 30 balls left and the team around 90. The one reliable batter made 29 and nobody after him reached 20.

I am not writing the words "temperament" or "bottlers" here. For years I have converted every such collapse into selection arithmetic, and the same applies. Pakistan's batting has exactly one load-bearing point — Babar. Of the three positions around him, none produced a 40 or a 50 that carried responsibility. That is a role-clarity problem, not a character problem.

And the roster composition deepens the doubt. The same XI that lists Babar Azam and Shaheen Shah Afridi also throws up names like Arafat Minhas and Hasan Nawaz, who are generally understood to be youth or development-level players, alongside "Shayan Acharya," a name I cannot place in any recognised senior Sri Lankan squad. The implication is direct: this could be a full-strength senior series, or it could be an A-team or emerging event — and the two readings produce entirely different conclusions. Until that is settled, forecasting the final is guesswork dressed as analysis.

Powerplay and death overs, audited from both ends

Start with the powerplay. Avishka Fernando made 16 off 17 — a strike rate around 94. In a chase of 111 that is harmless, because the required rate sat near six and nobody felt pressure. In a chase of 180, 16 off 17 is a structural problem, not a form problem. A slow powerplay is survivable only when somebody behind you bats at a 200 strike rate. Where that batter sits in this Sri Lankan line-up, the report does not say.

Now the death overs. Pakistan stopped at 110, which means wickets kept falling through the last five overs. A side that has lost six wickets by the 15th over usually squeezes 30 to 35 in the final five. Sri Lanka did what a side defending 110 should do — bowled for wickets rather than containment. That same instinct flips against you when you are defending 170, and the final will test whether Sri Lanka can tell the difference.

The middle overs — the stretch between 11 and 40, whether this is a T20 or a 50-over game — are the actual crime scene. Pakistan lost the match there. Sri Lanka won it there, first by taking new-ball wickets and then by parking Kamindu Mendis at one end. The highlights will show Madushanka's five and Kamindu's 62 not out. The highlights will not show the twelve overs in which Pakistan made 40 and lost three.

Kamindu's 62 not out: a low-leverage fifty

Kamindu Mendis finished 62 not out. On paper it is a match-winning innings. On the ground, a target of 111 never became pressure. The opening stand had already reached 50, the required rate never climbed above six, and the last 23 runs were never difficult. It is a good innings, but it is not evidence of form — it is a low-leverage half-century. An innings like that cannot tell you how the batter will handle a chase of 170.

There is another layer. The report lists Kamindu as an opener, while his usual senior usage has been in the middle order. If this is an experiment, it was conducted in the easiest possible examination — a 111 chase. The genuine test comes in the final, against a new ball, with 15 to 20 overs to bat.

The same scorecard shows Kusal Mendis out for 8 off 6. Two different Mendises — Kusal and Kamindu — get tangled in reporting more often than anyone admits, which is why I do not trust an innings sequence on first read. When a single report collides with its own sentences, questioning every conclusion downstream is the reader's right, not the analyst's irritation.

Where I could be wrong

The weakest part of my own argument is the part the report leaves empty — the sourcing.

First: the format is never stated. I inferred T20 from 17-ball and 6-ball innings references and a four-match league stage. If this turns out to be a 50-over match, my entire strike-rate argument collapses — 16 off 17 is a perfectly normal start there. Half of my case rests on an inference, and I will say so out loud.

Second: I assumed this is a senior international series. The roster names — Arafat Minhas, Hasan Nawaz, Shayan Acharya — point the other way. If this is an emerging or A-team event, then Babar's 29 does not mean "Pakistan's batting is in crisis"; it means "this was a trial match." The entire frame shifts.

Third: I read Pakistan's top position as fragility. It is entirely possible their earlier wins were by margins so wide that one defeat barely dented the NRR. That data is absent, so my "qualified but fragile" verdict is itself an inference.

Fourth: Madushanka's five-for may genuinely be an arrival. When a young left-arm quick finds rhythm once, he does not change a series — he changes a career. I have interrogated the number because the number is incomplete; that is not the same as saying there is nothing there. My habit is to doubt the reporting, not the player.

What I will be watching in the final

For me the tournament's biggest story is not Sri Lanka's win. It is Pakistan's 110, on the ground where the final will be played. My prediction: if Pakistan do not change their top three for the final, Sri Lanka's bowling will fold them inside 130 to 140 again. If they do change it, I want to know whether the change is role-based — someone promoted because he can handle the new ball — or reaction-based, because someone was dismissed last time.

The second thing going in the notebook: Madushanka's last four overs. If the final forces him to concede more than nine an over between the 17th and the 20th, then the five-for stops being a five-for and becomes a good day's arithmetic.

The third thing is England. Elimination is a fact. Everything after it — questions over the captain, a review of the coach, the "white-ball reset" essay — will come from press releases, not scorecards. I will read the pieces that tell me who actually played those three matches and in what format.

The honest summary is that I still do not have a trustworthy picture of this match — no balls faced, no economy, no NRR. I am not going to drop it for that reason, because cricket teaches you the most through the matches whose reports are incomplete. At 2:30 a.m. on a Gachibowli sofa during a World Cup, my clearest understanding came from the scorecard with the fewest numbers filled in.

And in that 36-person Zoom call, nobody asked who won. Everyone asked: "Who played besides Babar?" The final gets to answer that.