Not an Innings Stopped at 97: The 89-Run Ledger of Shadab, Haris and the Last Three Runs

Gus Atkinson's ball came in. Shadab Khan felt it hit the pad and stopped moving — at 97, he had already written himself off. The thick inside edge offered the opposite evidence before the umpire had to. That edge is where the match turns. Two balls later, back-to-back fours off the same England seamer, and the hundred was done. A massive six later in the same over dragged Pakistan's requirement down to three. Then Henry Crocombe bowled, and Haris Rauf drilled him straight down the ground for four. Pakistan captain Shaheen Afridi had no words left.

"I can't say anything," Shaheen said afterwards. "Shadab and Haris, the way they finished the game, an 89-run partnership. I've never seen anything like that in my life. I am really happy as captain — from the morning, the team effort was top drawer."

The lesson of this match is not in the last three runs. It is in the leverage each side held before the final two overs. At the back end of a chase the arithmetic looks simple — wickets in hand, runs needed, balls left. The simple arithmetic is the most deceptive part. Of the two men at the crease with the last wicket, one is a batter and one is a bowler who can hold a bat. The fielding side's plan then splits in two: keep the senior batter off strike, and pin the weaker one down to singles. Both halves broke down here, because Shadab controlled strike himself and kept finding at least one boundary an over.

Watching last-wicket stands for the better part of a decade, one pattern repeats: the pairs that win do not start by chasing runs, they start by splitting risk. Once it is settled who takes the risk on which ball, the rest of the arithmetic gets easier. In this 89-run stand, Shadab was the risk-taker and Haris was the buyer of time. In the final two overs those roles inverted — Haris had to look boundary-wards too, because the requirement had shrunk so far that a single dot ball would have brought the pressure back.

The real job of a last-wicket pair is not scoring runs; it is dividing risk between two people.

Atkinson's over was the hinge. When a seamer starts an over against a set batter in the nineties, his instinct is the yorker or the slower ball. Atkinson stayed on length, and Shadab used it. Two fours in two balls is not eight runs; it is a bowler's plan collapsing. He can no longer bowl his best ball, because he knows one miss can disappear for six. The six later in the same over came directly out of that pressure. Fourteen to sixteen runs in six balls rewrites the equation; a batter walking in needing three is then holding the match in his fist.

A cluster of boundaries in one over settles the result before the final over begins; the last over is then a formality.

One thing this win covers up is the eighty or ninety balls before it. The heroics of the final stand make it feel as though the match started there, when in fact it was built by the patience before. Shadab's journey from 97 to 100 was less about courage than about accounting — he knew which bowler he could take on and which over only needed singles. That accounting does not show up in any strike-rate table. A wage-efficiency metric is a flashlight, not a verdict: it shows who returns how many wickets per run, not who has the nerve to take risk on which ball.

Consider the paper trail. In Shadab's case the edge was the real witness, not the umpire's finger. I trust the paper trail more than the press conference. The sound off the bat does not lie; the post-match narrative often does. Shaheen saying he has never seen such a partnership is emotionally true, not statistically true. An 89-run last-wicket stand is rare, not impossible; the game has examples. What was genuinely rare is that the bowling side had one job — keep the senior batter off strike — and could not do it.

That is where the official version has its blind spot. The "unbelievable finish" headline conceals a weakness in England's plan. Why was the first ball of that over not a yorker to a set batter in the nineties? Why, defending three in the last over, did the field lean towards saving the boundary rather than stopping the single? A different call in either place and the story reads differently. Data analysts build pre-match maps that say things like "the number eight or nine plays straight, he does not sweep." But match rhythm does not obey the map; under pressure a batter breaks his own limits. Analysts have moved into the dressing room, and their conclusions often detach from the actual rhythm of the game.

There is another layer nobody usually prices. Shadab and Haris are both familiar franchise faces with different workload and contract calendars. Lower-order all-rounders are routinely undervalued at auction because their worth is measured in wickets and economy, not in batting role. An innings like this reprices them. An expiry date is not a deadline; it is a lever waiting to be pulled. So was that target of three — a lever the bowling side held and failed to pull.

The question now belongs to the next match. Is Pakistan's tail a plan, or has it simply been an accident all along? One win does not build a structure, but one win can force the structural question. For a captain like Shaheen that is comfort; for selectors it is discomfort — if an 89-run last-wicket stand is possible, why was the tail given so few balls in earlier matches? For England the question runs the other way: will the plan to close out games before the last over rest on the pitch alone, or also on a map of each batter's limits? The next series will answer it.