88 Runs After 154/9: Shadab Khan's 113* and the Story Left Outside the Scorecard

The score came up on a screen in Delhi — 154/9. About forty minutes later the same screen said Pakistan had won by one wicket. Between those two lines sit at least 88 runs, and nobody named them. I write the date first, because memory is a poor archivist and the beat is not. So my notebook also records that I saw 154/9 before I heard it — the difference between seeing and hearing matters later. The commentary box was already saying "Shadab's courage". My first question was what the other nine batsmen had done. The scorecard's answer to that question was 154. Nine wickets, 154 runs, a target of 242. The remaining 88 were added by someone else. That line — 154/9 — is the most honest line of this match, and the least read.

This report is filed from a distance. I was not at the Gaddafi Stadium in Lahore. I watched on a monitor in Delhi, and everything below rests on the broadcast feed, the scorecard, and calls with people who were actually there. I do not have the toss result, the pitch report, England's full innings card, the bowling figures, or even the name of the third team in the tri-nation series noted in my book. What I have is this: a match in Lahore, a target of 242, Pakistan at 154/9, a one-wicket result, and Shadab Khan unbeaten on 113. Wherever I step past the edge of that information, I will say plainly that it is inference, not fact. The source report was still being updated, which means no official post-match detail had been confirmed at the time.

The format is 50 overs, and its skeleton matters for reading this scoreline. Two new balls, a ten-over first powerplay, spin and set fields from overs eleven to forty, and the last ten overs of acceleration. Lahore's Gaddafi Stadium has historically been a batting ground — 300-plus is treated as normal here, and even 200 is routine in T20. Against that benchmark, a target of 242 looks light. Only three explanations hold: the pitch was two-paced or slow, England bowled with discipline, or Pakistan's top order stumbled. My information cannot separate those three. What I cannot separate, I will not write as a conclusion.

England touring Pakistan for a tri-nation series is not merely a sporting event. Inbound tours by the bigger boards are the spine of the PCB's international calendar, so England playing in Lahore is a balance-sheet event first and a result second. Four days in the Holkar corridor taught me to count footsteps before names, and that habit applied here — the headlines counted Shadab's name; I counted how many overs the first nine wickets took, and in what state they fell.

Now the arithmetic nobody did. Target 242, score 154/9 — subtract and you get 88. Since the match was won with one wicket standing, the final score should have been 243/9, which means the tenth-wicket stand was in fact 89. I am writing that difference down precisely because I do not have the official final total, and I will not round a number I do not know. Either way, a stand of 88 to 89 runs is the largest event of this match and the least measured. It sits at or near the top of Pakistan's ODI history for tenth-wicket partnerships — and I would want to check that against the ESPNcricinfo records before calling it a record, because declaring a "record" off a single match is exactly the carelessness I built a spreadsheet to prevent. A decade of data-gathering taught me one thing: in the last twenty years, last-wicket stands are the least documented phase in cricket analytics, because it is the only phase where one batsman cannot bat — and where the rules of decision-making invert.

That is where the real lesson sits. 154/9 is the repeatable signal; 88 runs is not. A top order that collapses to nine down is a pattern; a last pair adding 88 is variance. The result therefore showed the opposite of what it will be cited for — the proof of strength came from the part assumed weakest, the proof of weakness from the part the whole batting order rests on. I built a spreadsheet nobody asked for, and it became the only honest witness: those 78 Delhi Ranji matches and 143 innings taught me that second-innings collapses are never coincidence, they are habit. This Pakistan innings fits one of those columns.

Shadab Khan's innings has to be read in that same column. At 27, this is his first ODI century, and his first in a Pakistan shirt. His career average has sat in the mid-twenties and his strike rate in the mid-eighties — figures I still need to verify against a reliable source, so I will use them as direction, not proof. For a No.7 or No.8 all-rounder, 113 not out is a career outlier, not a new baseline. One innings carries effectively zero statistical weight for re-rating a batsman, and that is forgotten most reliably in the moment a hundred flashes on the screen.

His real value remains the bowling-first all-rounder package, not the batting. The scarce item in ODI cricket is a leg-spinner who can bat at seven or eight and bowl a full ten-over quota — that is a genuinely expensive slot in a selection ledger. This innings confirms the optionality of that package; it does not declare him a top-six batsman. For me the most transferable part of the innings is not the runs but the not-out. A 113 not out in a one-wicket win means he farmed strike, protected the No.11, and paced the chase by overs. That is a temperament signal, and temperament outlasts a statistic.

A warning belongs here, because what happens next morning is predictable. After this innings there will be a push to promote Shadab to No.6, and it would be a pure reaction to a single innings. That is the soft spot in every selection ledger — selectors re-price the innings they watched and ignore the innings played across the previous eighteen months. There is a second risk the noise of the hundred buries: this match contains a century and ten overs of bowling in the same body of work. For a bowling all-rounder, that is precisely the load profile that produces back and soft-tissue injuries. Shadab's injury record is pending verification in my notes, but a player whose injury file is not properly maintained is a subject for workload accounting, not celebration. I stopped treating the locker room as a quote factory years ago; what shows there is not a statement but the rhythm of fatigue.

England's side of it is equally clear, even without the card in front of me. One wicket needed, 88 runs to defend — calling that bad luck is easy, but it is an execution failure in the closing overs. The field was spread, the ball was old, and the spinner had the most to work with. Failing to take one wicket from there is a question of over management and line discipline, not strategy. Because I do not have the full bowling figures, I will not claim England's attack was under-strength — that would be the kind of inference I cut myself. I will say only this: the FTP squeeze around a tri-nation series means the bigger boards rotate their frontline seamers, so drawing conclusions about England's first-choice ODI side from this result would be premature.

And here the most common outside misreading surfaces: this win will be read as evidence of a "resilient team culture". The data says the reverse. 154/9 means the structure had broken and variance rescued it. A one-wicket margin is a thriller at result level and a failure at process level. Home weighting has to be added too — winning in Lahore and winning on the bounce of Australia or New Zealand are different skills, and this match says nothing about the second. The coverage maths says the same: the media's entire foothold sits in the last ten overs, and nobody keeps a timesheet for the first thirty-five. The night desk taught me that the quietest shift writes the first draft of morning; here the quietest shift was the innings nobody turned into a clip.

For the source report to be "still updating" means one concrete thing: this piece predates any post-match controversy. In a one-wicket finish, a dropped catch or a DRS call is routine, and if one surfaces, the whole frame shifts from heroic comeback to mixed competence. Until that detail arrives, I hold my verdict — that is the habit, and it is the habit that has kept a single match report off my desk in nine years without one detail the scorecard or the broadcast could not supply.

The next internal signal is not the score but the team sheet. Watch the XI for the next match: does Shadab bat at six or stay at seven, and does the top four change at all. If selectors use 113 not out as grounds for promotion, they have given one innings the status of ten seasons. If they look at 154/9 and fix that, they have done what the spreadsheet says. The question is not that Pakistan won by one wicket. The question is who rescues 154/9 the next time it happens.