From 154/9 to 243/9: Shadab Khan's 113* and an 89-run last-wicket stand take Pakistan past England by one wicket

Hook: The scoreboard at the 34th over, and a number that told us nothing

After the last ball of the 34th over, the Gaddafi Stadium scoreboard in Lahore read 154/9. Pakistan needed 89 more to win, with only Shadab Khan and Haris Rauf at the crease. I was not looking at the scorecard; I was looking at the over-by-over log, where Haris Rauf's name sat next to 7 runs off 19 balls, a strike rate of 36.8. This is the same Haris Rauf whose batting sample had rarely stretched to 20 balls. When you learn that the fate of the match rests with a batter who has made 7 off 19, you stop watching cricket and start watching a probability problem.

I took the match apart to see which part was still warm. The warm part was not Shadab Khan's innings. It was England's last sixteen overs. Shadab made 113 off 96 balls, with 13 fours and 5 sixes — 82 of his 113 runs, 72.6 percent, came in boundaries. For a No.8 batter, that is the number of an evening, not the number of a technique. And a match decided by one evening does not testify to a team's strength; it only records what the other team failed to do.

Pakistan won by one wicket with 17 balls to spare, 243/9 in 47.1 overs. England had been bowled out for 242 in 47.4 overs. A one-wicket margin does not describe superiority by either side; it describes two teams losing the third phase of their innings in opposite ways.

Context: a Lahore match whose conditions were half-reported

This was a group match of a tri-nation series, not an ICC global event. The news value halves inside 48 to 72 hours, but the archival value holds, because the unbroken 89-run tenth-wicket stand is being reported as the highest in a successful ODI chase. Two things are true at once and must be kept apart.

Pakistan won the toss and chose to field. England's first lesson arrived in the fifth over: 19/3. Tom Banton 4, Joe Root 5, Harry Brook run out 1. Pakistan's first lesson arrived in the seventh: 31/3. Fakhar Zaman 10, Saim Ayub 6, Babar Azam 10. Both innings were wrecked in almost identical fashion at the start. That is itself a technical signal: with two new balls in an ODI, shine exists at both ends, and if the surface offers early assistance, both top orders fall the same way. This is not the story of one team's technical collapse.

What the report does not say matters just as much. Pitch type, grass cover, day versus day-night status, dew: none of it is in the available information. Which means I cannot price the toss decision. A 242 all out and a 243/9 chase is inconsistent with a 320-par surface, so some assistance was likely — Liam Dawson's two wickets and Arafat Minhas's 2/26 point that way. But that is inference, not measurement. Where there is no data, I will not issue a verdict, and that is the most honest technical point of this match.

Pakistan's attack was rotated and second-string. Naseem Shah was injured, Razaullah debuted, Haris Rauf was in the XI. The attack that bowled England out inside 48 overs was not Pakistan's full-strength statement. Extrapolating from this result to Pakistan's bowling depth would be premature.

Core: England lost the match from the 34th over to the 48th, not in the powerplay

Freeze England's innings at one point: 145/4. Ben Duckett had 105 off 111, strike rate 94.6, ten fours and two sixes. It was his fifth ODI century and accounted for 43 percent of England's 242. The fifth-wicket stand between Duckett and Tom Curran was worth 126 — a rebuild that was necessary and that consumed the entire acceleration window.

Curran's 42 off 52, a strike rate of 80.8, is sub-par for a No.5 or 6 in a 50-over innings, especially with three wickets in hand past the 30th over. From 145/4 to 242 all out is 97 runs for six wickets. England's real defeat is recorded there, not in the powerplay. The 19/3 start was survivable and was survived, to 145/4. What could not be survived was failing to turn 145/4 into 280.

There are two parts to that. First, England never lifted the run rate even while Duckett was set. Second, they folded entirely in the last ten overs, bowled out with 20 balls remaining — the innings finished at 47.4. A 50-over innings ending at 47.4 is its own story: the team never got the chance to bat out.

Shaheen Shah Afridi's spell is the cleanest proof: 4/46 from 8.4 overs, economy 5.31, and his 150th ODI wicket along the way. Bowling 8.4 overs as captain of a rotated side is a moderate workload, but it shows his spell covered both the new ball and the death — the two decisive phases. England's collapse is recorded alongside his spell.

Core: For about 75 percent of the chase, Pakistan were losing

31/3 in seven overs. Saad Baig's 32 off 22 bought some breathing room. Then 103/6, 122/7, 131/8, 154/9. That is a straight line, and at no point on it was Pakistan in a position to win. A winning graph in cricket measures how long a team was near victory. For roughly three-quarters of this chase, Pakistan were plainly the inferior batting side.

This is where the scorecard and the match diverge. Read 243/9 against 242 and you would say it was an even contest. It was not. It was a lopsided contest that one extraordinary innings and one extraordinary bowling failure reversed.

Core: Shadab Khan's 113* — a number of circumstance, not technique

Read the innings in three layers. Layer one: 113 off 96, strike rate 117.7. A No.8 century in an ODI is a rare event; No.8 batters typically average in the low twenties at a strike rate of 85 to 95. This innings sits far above his own distribution. Layer two: 82 of 113 in boundaries, 72.6 percent. Finishers usually run 55 to 70 percent; 72.6 signals a boundary-or-block method. That is not sustainable against a hard new ball or a spread field. Layer three: context. Batting with the tail, fielding restrictions gone, the opposition in defence mode. There is no more favourable setting for a lower-order hitter.

One gap must be flagged. The available information contains no bowling figures for Shadab — no wickets, no spell. He was picked as the spin-bowling all-rounder, replacing Faheem Ashraf, and he won the match with his secondary skill. That is entertaining, and it also sits awkwardly against the selection logic. Note too that he was a recalled player, outside the first-choice XI. Selection status is itself a form signal.

Core: Shadab carried about 92 percent of the scoring in an 89-run stand

From 154/9 to 243/9 is 89 runs off roughly 79 balls, a partnership strike rate near 113. Of those 89, Haris Rauf made 7. Shadab carried about 92 percent of the scoring alone. Haris's contribution was survival, not scoring: 19 balls unbeaten, far outside his batting distribution. Calling this partnership a strategy would be wrong; it is a low-probability event that happened once.

The technical question on the other side is: where was England's field while those 89 runs were made? With nine wickets down, the fielding side has no score to protect and no visible reason to keep a catcher in — the risk of an attacking field is theoretically zero, because one wicket ends the match. When you lose scoreboard pressure, you hand the batter the easiest thing cricket offers: permission to watch and leave. Field placement is not recorded in the report, so I am keeping this as a plausible contributing factor, not a verdict. But if a team concedes 89 from the 34th over to the 47th against a No.8 and a No.11, at least one tactical choice went wrong.

Core: another number the report did not carry

England had a set centurion at 145/4 and made 97 more runs in the rest of the innings. Pakistan were 154/9 in the 34th over and made 89 more without losing a wicket. One team had a batter; the other had only bowlers. The side that extracted more from its bowlers won. Turn it around: the runs England's middle order failed to extract were the runs its bowlers gifted back. That is where the match turned, not in a single shot.

Contrarian: a one-wicket margin lies, and so does a record

My real objection is not to the result but to its interpretation. Treating a one-wicket win as evidence of Pakistan's batting strength is a category error. Their top order was three down for 31 inside seven overs. An 89-run tenth-wicket stand is not a repeatable process; it is a low-probability event. Draw a lesson for the next match from this innings and you are building a rule out of an anomaly.

The second objection concerns time sensitivity. This match has a genuine political layer — presidential and prime-ministerial statements carry it from the sports page into state narrative. When that happens, two things rise together: newsworthiness and the risk of distortion. For me this match is an 89-run stand, not a national story. Turn it into one and I repeat the error made at every big occasion.

The third objection is about data honesty. Scorecard-level figures — Shadab's 113*, Shaheen's 4/46, the 89-run record — should not travel further without independent cross-checking. And it is worth recording that the model I ran for this match told me nothing about the pitch. One ground, one surface, no grass information: the model is silent. Same grid, different ground, and this time the grid knows nothing.

Takeaway: what I will watch in the next match

Next match I will not be watching Shadab's runs. I will watch how many overs Pakistan's top order survives against the new ball, and whether Shadab is kept at the same No.8 with the same responsibility. On the other side, I will watch England's run rate from the 35th over to the 50th. If it collapses to 97/6 again, the 89-run stand was one evening's miracle. If it does not, I recalibrate the model. The spreadsheet has the answer before the commentary box does — the question is who is right this time.