From 154/9 to 243/9: Shadab Khan's 113* and the Partnership That Was Never a Partnership

The Balls Nobody Counted

When Pakistan were 154 for 9, Shadab Khan was on roughly 30. When the match ended, he was on 113 not out. The arithmetic that follows is unavoidable: of the last 89 runs, roughly 80 were scored by one batter. Rauf's contribution was 7 off 19 balls. That is 7.9 percent of the stand.

The scorecard calls it an unbroken 89-run last-wicket partnership. The sentence is not wrong. It is right in the way a company's annual report is right when it calls a loss negative growth. Partnership implies two roughly comparable contributions. This was a 92-to-8 split wearing a shared noun.

The one sentence that framed the entire match is the same sentence that buried its largest part.

I come at this from football, where we have our own version of the lie: possession is not control, it is a story we agreed to tell. Cricket's version of that story is the partnership. A team can hold 70 percent of the ball and lose; a stand can run to 89 and belong to one man.

Context: 241, Twenty Balls, and a Third Country Nobody Named

Start with what is known. England were bowled out for 241 in 46.4 overs. Ben Duckett made 105, which is 43.6 percent of the total. Shaheen Afridi took 4 for 46. Two ODI debutants, Arafat Minhas (2/26) and Razaullah (2/38), took four wickets between them for 64. Three bowlers accounted for eight of the ten wickets — 80 percent.

Pakistan reached 243 for 9 in 47.1 overs, with 17 balls unused. The run rates were near-identical: England 5.16, Pakistan 5.15. A one-wicket win, a two-run margin.

Now the part the record does not contain. The match is logged as the fourth fixture of a Pakistan ODI tri-series. A tri-series has three teams. The third team is not named anywhere across the entire record. Every one of the 36 information points carries a source field reading none — no wire service, no scorecard reference, no byline, no dateline.

I have spent the last few years logging every Indian football committee, election and court date into a tracker, and the habit does something to your eye: it makes the unremarkable thing the first thing you notice. What I notice here is a match report with no third team and no sourcing. The numbers are internally consistent — 241 in 46.4, 243 in 47.1, 17 balls left — which suggests a real scorecard underneath. The packaging suggests aggregation.

Everything below is arithmetic on the given points. Where there is no data, I will say there is no data. That is the habit of a man who once publicly flagged that he had none.

Core: Re-Reading the Scorecard

1. The clock was lying

The first derived finding is also the least reported fact of the match: Pakistan had more time at 154 for 9 than the scoreline made it feel.

Run the budget. Shadab finished on 113 off 96 balls. If he was on about 30 when the ninth wicket fell, he scored roughly 83 more off roughly 66 balls. Rauf faced 19. That puts the stand at approximately 85 balls. The innings ended on ball 283, which places the ninth wicket near ball 198 — about the 33rd over.

At that moment Pakistan needed 89 off 102 balls. The required rate was about 5.2. It never crossed 6.5 at any point in the chase.

The panic was in the scoreline, not the clock.

This matters because the default report will call it a thriller that went to the last over. It did not go to the last over; it finished with 17 balls unused. And if the clock was never squeezing, Shadab's task was technically easier than it looked, because he never had to force risk. He had to survive and pick his moments. A batter with no reason to hurry is the most dangerous batter on the field.

2. The acceleration curve

Put three numbers side by side and the innings maps itself. First fifty off 52 balls, strike rate 96.2. Second fifty off 40 balls, strike rate 125.0. Last 13 runs off 4 balls.

That is not a normal curve. A normal curve climbs. Here the first 52 balls sat below a run a ball — inside an innings where wickets were falling at the other end. No batter slows down deliberately while his team slides to 154 for 9 unless he has worked out that aggression is the actual death.

Shadab suppressed risk for 52 balls while the innings collapsed around him, then inverted the risk profile the moment the field was forced to come in.

This is situation-reading, and it is the most transferable technical signal in the match. Note what is absent: no new shot, no innovation, no structural idea. Pure execution. Which is exactly why it is fragile. Execution does not repeat on demand; structure does. Pakistan did not have structure here. They had a man.

3. 72.6 percent: boundary or wait

Of Shadab's 113, eighty-two came in boundaries — 13 fours and 5 sixes, 18 in all. That is 72.6 percent of his runs, at one boundary every 5.3 balls.

Now invert it. The other 31 runs came off roughly 78 balls, a strike rate near 40.

That is the number that will be skipped and the number that explains everything. He was not accumulating. He was waiting. Thirty-one off 78 means he was leaving calmly, not scrambling for singles, choosing each boundary ball on his own terms. That is the hardest form of risk management there is at the last wicket, because you have zero margin and you are still refusing to hurry.

This is also where I have to be honest about a gap. There is no field-setting data in the record, no bowling-change data, no wagon wheel. What I can say is that if a batter can make 31 off 78 balls and still finish 113 not out, England's plan to contain him was not working. What I cannot say is what that plan was.

4. Two currencies: Rauf's seven

Rauf made 7 off 19. Seven point nine percent of the stand. Read superficially, that is a nothing stat.

I read it differently. Rauf's seven runs were negative value in the scoring currency and maximum value in the survival currency. Those are different currencies and they cannot be exchanged.

Eating 19 balls is not trivial. A tailender who lasts 19 deliveries hands his partner 19 deliveries of breath. Shadab could not be dismissed during those balls because he was not on strike. That is real contribution.

And here is the point of the whole piece: any narrative that frames this as Rauf's heroic support is measuring the wrong thing. Pakistan scored 89 for the last wicket and roughly 80 of them came from one bat. The moment you read that sentence, the partnership frame collapses. It was not a partnership. It was a one-man survival operation with a blocker at the other end.

5. England's mirror

Turn to England's innings, because the pathology is identical, just inverted.

England were bowled out for 241 in 46.4 overs — 280 balls faced, 20 unused. More than three overs. Their run rate was 5.16. Those twenty balls, at that rate, are about 17 runs. The match was decided by two.

England did not lose by a wicket. England lost by the twenty balls they never used.

That is the cleanest, most checkable finding in the match, and it will appear in no report, because it does not show up in the scoreline. Twenty unused balls is roughly seventeen runs against a two-run margin. England's defeat was not a batting-quality defeat. It was a failure to bat out the innings.

And England's innings carries the same mirror distortion: one batter at 43.6 percent. The other 136 runs came from nine batters. That is not an innings, that is a subsidence. 241 was not a collective effort; it was one man and nine requests.

Add the bowling shape. Three bowlers took 80 percent of the wickets. England's lower order was breached by a narrow attack. A team whose bottom half folds to three bowlers does not leave twenty balls unused by accident — that is structure, not coincidence.

6. Managing the tenth wicket

Here is the question that should be asked hardest and has the least data behind it.

England reduced an opponent to 154 for 9 and lost. Losing control in the final ten percent of a task is a control failure. It was not a failure of the total — 241 is not a disaster — it was a failure of phase management.

But I have to stop and say plainly: I do not know the mechanism. The record does not say how aggressive the field was, whether the No. 11 was deliberately exposed to strike, whether the set batter was starved of it, who bowled which over. Those are exactly the details that constitute analysis, and they are all absent.

What I can say is this. When a side goes from 154 for 9 to a defeat, captaincy error is easy to infer and impossible to prove, because the evidence was on the field and not in the card. I will not infer. I will only log that the most important question in this match is the one no report answers.

7. Two debutants: a selection statement, not a structure

Two ODI debutants in the same attack — Minhas 2/26, Razaullah 2/38 — is a statement about selection. It is not a settled structure.

The XI that won this match is not the XI that will win it repeatedly.

This is my strongest objection to the framing of the performance. Playing two uncapped quicks together makes sense when you are rebuilding and results are secondary. When results are primary, you play one, not two. Pakistan played both and both delivered, which is the good news. It is also the news that the bowling structure is not yet decided.

One good day of bowling and a settled attack differ in what they hand you: the first gives you a match, the second gives you a series. Pakistan got the first.

Contrarian: Where I Could Be Wrong

Now the section people like me write least.

First: my entire inversion rests on an estimate. I derived that Shadab was on about 30 at 154 for 9 by subtracting Rauf's 7 and assuming some extras. I do not know the extras. If they were 10 to 12, Shadab's share of the stand drops from about 80 to about 70, and the partnership frame looks less dishonest. My conclusion would hold in direction and weaken in force. And I derived the figure at medium confidence, not high.

Second: maybe the partnership frame is right and I am over-reading. Suppose Rauf had been dismissed in those 19 balls. Shadab comes on strike, bowlers get a full over at him, the field spreads. Survival value becomes concrete. I accept that. My objection is not to the value of survival; it is to merging survival and scoring into one story. Two currencies, both real, not convertible.

Third: maybe the real story is England's batting, not Pakistan's chase. 43.6 percent, 20 unused balls, 80 percent of wickets to three bowlers — that all points at England. I accept the case, which is why it gets its own section. But being bowled out for 241 is not unusual for England; winning from 154 for 9 is unusual. Build the story around the rare event, not the common one.

Fourth, and biggest: this innings must not be called great. A 243 chase is not a great chase. Great chases are 300-plus, where the required rate starts above six and every over costs you something. Here the rate never passed about 5.2. What was great was the construction of the innings, not the size of the chase. Anyone writing this up as an all-time chase is making the mistake I am trying to avoid.

Fifth: the reverse-consensus trap. I know my type. We turn every compliment inside out to look clever. Shadab's 113 not out off 96 in a one-wicket win was bad because he was slow — that sentence is as lazy as the hagiography it replaces. Let me say it cleanly: 113 not out off 96 balls in a one-wicket win is a genuinely large innings. I am not disputing it. I am disputing the frame that files it alongside another man's seven.

Sixth: maybe the missing third team means nothing. It could be an editing slip. I will not inflate it. But when a record has no third team and no source behind any number, every conclusion drawn from it deserves an asterisk. Mine has one.

Takeaway

Here is my prediction, written so it can be falsified, because I keep a running list of my own wrong calls.

The next time Pakistan's top order collapses like this, they lose — unless the set batter is scoring above a strike rate of 110 through the last fifteen overs. Shadab's acceleration curve was a rescue, not a system. Rescues recur. Systems recur on schedule.

And for England: if the next innings also leaves twenty or more balls unused, the problem is not individual batters, it is lower-order planning. Twenty balls is about seventeen runs. Giving away seventeen runs for free in a one-day international is a habit that selection fixes, not coaching.

The question is not how many Shadab scored. It is whether, the next time a scorecard tells you there was an 89-run stand, you believe the sentence or count the balls.

Every scorecard is a train window: you see what you want. Through the 154-for-9 window, most people saw a story. I saw one man, and beside him another man doing nothing but stopping deliveries.