From 154-9 to 243-9: Shadab Khan's Innings, and What England Lost in Lahore

Gaddafi Stadium, Lahore. The 34th over ends and the board reads 154-9. Nine wickets are gone, Haris Rauf is at the other end — a batter whose ODI batting record has never sat in the reliable lower-order bracket — and Shadab Khan is on 31. Pakistan need 89 from 96 balls. On paper the required rate is a modest 5.5. On grass it is close to impossible, because the next ball can end the match.

I opened the ball-by-ball ledger and found the scorecard. The remaining 79 balls produced 89 runs. Of those, 82 came off Shadab's bat. Haris Rauf faced 19 balls and made 7, without a single boundary. That is 92 per cent of the scoring in an unbroken stand delivered by a player who had been recalled to the side as a spin-bowling all-rounder — and whose bowling figures appear nowhere in the original match report.

— Root: 2026 Cricbuzz Ball-by-Ball Ledger | Scenario: opening a long-form data investigation where the official record is incomplete

This innings will be remembered as the highest tenth-wicket stand in a successful ODI chase. It should also be remembered for covering a match in which England were the better batting side, and in which Pakistan's top order had already handed over the full map of its weakness inside seven overs.

What the match was, and what the report did not carry

This is not an ICC global event. It is a tri-nation series group match, in Lahore, on a Sunday. The format is ODI: fifty overs, two new balls, shine available at both ends early. Pakistan won the toss and fielded. One selection detail is documented: Razaullah debuted in place of the injured Naseem Shah, with Haris Rauf back in the XI. Pakistan's seam attack was rotated and second-string. Shadab Khan returned in place of Faheem Ashraf — a form signal in itself, because when a player who was outside the first-choice XI wins you a match, the question is not how good he is but what data kept him out.

England's innings has a simple shape: 19-3 inside five overs (Banton 4, Root 5, Brook run out 1), a 126-run fifth-wicket stand between Ben Duckett and Sam Curran, then 145-4 collapsing to 242 all out in 47.4 overs. Pakistan's chase: 31-3 inside seven overs (Fakhar 10, Saim 6, Babar 10), Saad Baig's 32 off 22, then 103-6, 122-7, 131-8, 154-9, and finally 243-9 in 47.1 overs. Seventeen balls were left.

Now the part the original report does not contain, and without which no conclusion holds. The pitch type is not stated — no grass cover, no read on pace or grip. Whether it was a day match or a day-night fixture is not stated either, and dew in a Lahore evening chase would materially change the reading of the final partnership. No rain or DLS involvement is reported. Most important, every data point carries 'Source: None' while the photograph is credited to Reuters: the numbers are in-house match reporting, not agency wire, and must be cross-checked against ESPNcricinfo or Cricbuzz before any model uses them.

— Root: Data Monk skepticism and INTJ systems thinking | Scenario: auditing a polished analytics claim

19-3 was a start, not the cause of death

The commentary box will say England lost in the powerplay. Nineteen for three in five overs, three wickets including a run out, sounds decisive. The ledger says otherwise: that position was survived. Duckett and Curran put on 126 for the fifth wicket and the side reached 145-4. The powerplay damage had been absorbed.

The loss happened afterwards. From 145-4 to 242 all out is 97 runs for six wickets. At a venue like Lahore, a side with a set centurion at around 30 overs normally targets 290 or more. England lost their acceleration phase entirely. That is not an opinion; it falls out of the innings shape. If four wickets are down before the 25th over and you fold for 242, your No.5 and No.6 did not convert.

Curran's 42 off 52, a strike rate of 80.8, is the cleanest evidence. In a fifty-over innings, a No.5 or No.6 batting at 80 stabilises the innings and stalls it in the same motion. The rebuild itself was correct — at 19-3 it was necessary. The failure was not converting the rebuild into acceleration. In my 2026 phase coding, this was the most repeated pattern of all: a line like '42 off 61' means nothing without phase, match state and required rate attached to it. Here the required rate was static and the partnership was growing, and that was the actual problem.

— Root: 2026 Cricbuzz granular-data work | Scenario: explaining why raw match data needs interpretation

Duckett's innings sits awkwardly in this review. 105 off 111, ten fours, two sixes, a strike rate of 94.6, and 43 per cent of England's total. The anchor role was correct when the side was 19-3 — this is one of the rare cases where questioning the anchoring would be wrong. But one detail belongs in the record: 52 of his 105 came in boundaries, roughly half. The other half was rotation, and 94.6 is the strike rate of an innings that carries a side to 242, not 290. That gap was settled in the last ten overs, by which point Duckett was gone.

The real face of Pakistan's chase

The shape of the second innings mirrors the first, and this is the most interesting structural fact of the match. Both sides lost three wickets inside seven overs: England 19-3 in five, Pakistan 31-3 in seven. When both top orders fall like that, the conclusion cannot be that one team collapsed technically. It means the surface offered early assistance, or both new-ball attacks were genuinely good, or both. I do not have a pitch report, so I record it as uncertain — but two spinners taking four wickets between them (Dawson 2, Arafat Minhas 2-26) points to grip or turn, or at least to the absence of express pace. A 242 all out and a 243-9 chase is not the profile of a 320-par belter.

Inside the chase, Pakistan deteriorated steadily. Saad Baig's 32 off 22 was the only innings that gave the middle overs any tempo, and it was brief. 103-6, 122-7, 131-8, 154-9 is not a partnership-based chase; it is an innings in which the lower order fell one at a time while a single end held.

One thing must be said plainly, because without it the whole analysis dissolves: for roughly 75 per cent of the chase, Pakistan were the clearly inferior batting side. A one-wicket margin does not mean the teams were level. It means one extraordinary individual innings and an English death-phase breakdown combined to produce an outcome that came from an event, not a process. Reading this as evidence of Pakistan's batting strength is a category error.

Shadab's innings: the method, and the method's limit

113 not out off 96, strike rate 117.7. Thirteen fours and five sixes: 82 of 113, or 72.6 per cent, in boundaries. For a No.8 that is exceptional, but the way to read it is as a style signal rather than a sustainable method. Finishers typically take 55 to 70 per cent of their runs in boundaries; 72.6 indicates a boundary-or-block approach rather than rotation-based accumulation.

That choice was rational in the situation he was in: nine down, field spread, catchers out, and no reason left for the fielding side to attack. In that setting, boundary-or-block gets cheaper, because there is no need to take risk for twos and space exists for fours. The same method kills itself in a different setting, against a hard new ball or with catchers in place. Reading 113 not out as proof that Shadab is now a top-six batter would be wrong.

One more thing belongs here and is entirely missing from the report: his career baseline. His ODI batting average has sat well below top-six level, but no career figure is given in the source, so I cannot compute the deviation arithmetically. What I can compute is that he was recalled to the XI, and selection status is itself a form signal. The right question about a player who was outside the first-choice side and then won a match is not how he won it, but which data kept him out.

— Root: 2026 UAE IPL toss-myth investigation | Scenario: writing about uncertainty, failed hypotheses, weak signals

Haris Rauf's nineteen balls

The scorecard line reads: 19 balls, 7 not out. Most readers will move on. I stop, because that number is a technical event. His batting distribution does not produce innings like this. Surviving nineteen balls at the death while your partner scores off almost every second ball is a skill the scorecard conceals behind '7*'.

The split inside the stand is clean: 7 of the 89 to Rauf, 82 to Shadab — 92 per cent of the scoring carried by one batter. Had Rauf been dismissed off any one of those nineteen balls, and on his career numbers that was not a small probability, this match is lost by a wide margin. The correct description of the stand is not that two batters won it together. It is that one batter carried the innings and the other refused to let it fall. Those are different skills, and the second one is statistically invisible.

Shaheen's spell, and the weight of captaincy

4-46 from 8.4 overs at an economy of 5.31 is the best bowling performance of the match, and it came at both ends: the new ball and the death. It also brought up 150 ODI wickets. Bowling 8.4 overs as captain of a rotated side is a moderate workload, not an extreme one — and that is the point. If the captain only gets 8.4 overs out of his best bowler, the question is who bowled the last eleven, and why England's lower order were allowed to take 89 from them.

The biggest tactical decision of the match is hidden there. England's death bowling and fielding operated in a situation that demanded no pressure: nine down, one wicket left, no reason to keep catchers in. That conservatism is understandable. Its consequence was that Shadab never needed to risk singles and kept finding space for fours. Eighty-nine runs for the tenth wicket is not only one batter's ability; it is also a document of the fielding side's tactical passivity. I record that as a plausible contributing factor rather than a proven cause, because I do not have ball-by-ball field placements. What I do have is the runs: 79 balls, 89 runs, no wicket.

The night the scorecard does not contain

One inference about the pitch is necessary, because without it we weigh both innings on the wrong scale. 242 all out and 243-9 in reply suggests run-scoring was not easy. Four wickets between two spinners strengthens that. From there comes an uncomfortable conclusion: if the pitch was difficult, England's 242 was not a terrible score, and Pakistan's 154-9 was equally explicable. That does not make the match ordinary; it makes comparison with a 320-par ODI useless.

— Root: 2026 UAE IPL empty-stadium study | Scenario: myth-busting long-form feature

The convenient story, and its cracks

Now the part I write every time and every editor wants removed: this result is not proof of a process.

First, the strongest version of the opposing case. England's death bowling really was poor — 89 without a wicket in the last 79 balls. England really did lose their acceleration phase — 145-4 to 242. Both failures are real, both are in the record, and neither can be dismissed as luck. If I run the situation through my phase model, win probability at the fall of the ninth wicket in the 34th over sits in single digits; that is a model estimate, not evidence, and I present it as such.

Now the cracks. One batter making 113 off 96, with 72.6 per cent in boundaries, is not a repeatable process. It is a low-probability event. An 89-run tenth-wicket stand is as rare in cricket as a 90th-minute goal from a goalkeeper in football. It happens, it should be recorded, and it should not be called a strategy. If Pakistan find themselves in the same position next match, the probability of a repeat is very low.

The second crack is in the narrative that will form around this result. Presidential and prime-ministerial statements lift the outcome off the sports page and into state narrative. That raises newsworthiness and distortion risk together. When a group match becomes an object of state praise, the questions inside the match — why Pakistan's top order loses three wickets in seven overs — stop being asked. Those questions matter more than the win, because they repeat.

The third crack is the ring of round numbers around this match: Shaheen's 150 ODI wickets, Duckett's fifth ODI hundred, Shadab's 113 not out, the tenth-wicket record. The most overrated number in Indian cricket coverage is the round one, and here it happened again. '150 wickets' is an achievement; it does not say in which phase, against which batter, with which field. '105 runs' is a number; it does not say why the acceleration never came inside the same innings.

— Root: Data Monk skepticism | Scenario: testing a polished claim against the scorecard

What the report left out is the biggest question

The source carries no bowling figures at all for Shadab Khan — no wickets, no overs, no economy — even though he was picked as the spin-bowling all-rounder in place of Faheem Ashraf. He won the match with his secondary skill, and his primary skill is absent from the record. That is a reporting gap, and it is the most useful part of this piece: anyone building a model needs to know which player contributed in which role.

England's bowling figures are similarly incomplete. Who bowled which overs inside that 89-run stand, who bowled the last eleven, is not recorded. What I have is the spinners' contribution: Dawson's two wickets and Arafat Minhas's 2-26. Without the rest of the picture, 'England's death bowling was poor' is a direction, not a conclusion.

This is where I have to fight an old habit of the trade: once the outcome is known, every ball becomes 'the plan'. Every Shadab boundary turns into a calculated risk under pressure and every six into the fruit of a plan. The correct method is to judge each decision only with pre-ball information — field setting, the bowler's previous over, the required rate at that moment — and to publish the balls where the plan visibly failed. Shadab's innings contains edges that survived and balls that passed through a field with no catchers. Leaving those out is not reporting; it is promotion.

What to watch next

For Pakistan, the real signal is not 113 not out. It is 31-3: three wickets in seven overs, Fakhar, Saim and Babar. If that pattern repeats, Shadab will be asked to rescue the side from 154-9 again, and that cannot be repeated. The top-order collapse is more repeatable than the win, which makes it more important.

For England, the question is not the powerplay. It is who decided the route from 145-4 to 242, and why. If the No.5 and No.6 strike rates sit near 80 again next match, that is not a one-match issue but a selection philosophy.

And one question has no answer in this report, so it stays open: was that Lahore pitch getting easier in the evening? If it was, part of those 89 runs off 79 balls belongs to the weather, not to a bowling failure. If it was not, England's death plan deserves a hard audit. The report does not say whether the match was day or day-night. That single line should be recorded first next time, because without it everything else is inference.

The biggest lesson of my 2026 ledger was this: a scorecard is a summary, written under time pressure. When I look at the gap between 154-9 and 243-9 today, I see what I saw then — the record is incomplete, and the gap has to be filled with counting, not with a story.