Lahore's 89-Run Record Is Real. So Is the Top-Order Collapse It Buried.

The highlight reel from Lahore carried three numbers: 113, 89 and 241. The number it left out was 154/9, and that is the most honest figure the match produced. A target of 242, 88 still needed, one wicket left, and Haris Rauf at No. 11. What the match report called a miracle is, in the language of a model, a very low-probability positive outlier. I am calling that an estimate and not a statistic, because no official scorecard has reached me, there is no ball-by-ball data, and nobody has recorded how many balls remained when the winning runs came.

What is recorded is this: Shadab Khan made 113 off 96 balls, his maiden ODI hundred, and Rauf finished unbeaten on 7 and hit the winning runs. Both facts stand, and I am not here to shrink them. My quarrel is with the frame being sold alongside the win — the miracle frame, which from tomorrow will quietly cover Pakistan's actual top-order problem. There is a version of this story where the data wins. This is not it.

What actually happened in Lahore

This was a tri-series ODI involving Pakistan, England and Sri Lanka, played in Lahore. England batted first and slid to 19/3. Ben Duckett held the innings together with 105 off 111 balls, yet the side were bowled out for 241. Shaheen Shah Afridi took 4 for 46; Razaullah took 2 for 38. The report describes the pitch as batting-friendly, which is the input my entire par-score calculation depends on and the input that makes me most uncomfortable.

In reply, Pakistan lost their top three inside the powerplay. They reached 154/9 — 88 runs short and down to the last pair. From there Shadab Khan and Haris Rauf put on an unbroken 89, the highest tenth-wicket partnership in a successful ODI chase. The target was met, the match won by one wicket, and Pakistan moved into the tri-series final. England, per the report, had already lost their first two matches; this was must-win, and the third defeat ended their tournament.

Here is the part the report does not carry, and my whole method rests on saying it out loud. Shadab's bowling figures are nowhere recorded, so I hold only half the data on his all-round value. Nobody states how many balls were left at the finish — possibly several, but it cannot be established. There is no mention of dew, weather or DLS. The consequence is simple: every par-score or win-probability claim I make in this piece lives inside a bracket, never as a verdict.

The 241 question, and its limits

On a Lahore surface described as batting-friendly, being bowled out for 241 after an opener's hundred is the first leak on my sheet. I will not call it a finding. Without over-by-over data I can only offer brackets: if England's last ten overs produced more than 80, then 241 was par on that pitch and my complaint is empty. If their last five wickets fell for 40, the total was 25 to 30 short. Which of those is true I do not know, and what I do not know I will not print as fact.

One thing needs no model. England were bowled out. In a 50-over innings, being dismissed means you did not spend your full quota, and unspent overs are unearned runs. That is the par leak visible without a spreadsheet. In modern ODI cricket, a total bleeds fastest exactly where an innings ends early. England made 241 but never bought all their overs — and that gap is what became an 89-run last-wicket stand.

Duckett's hundred deserves one cold sentence. A hundred off 111 balls is a strike rate near 94.6. Coming in at 19/3, that is a solid innings and I will credit it. The question is not his strike rate; it is how much runway his rebuild left for the last third of the innings. The scorecard answers that, not the highlight — and the scorecard is not in front of me. Medium confidence, published so I cannot quietly forget I said it.

Shadab's hundred: the real story, on half the data

113 off 96, a strike rate around 117.7, batting at No. 8, in a chase, after eight wickets had gone. Middle and lower-order ODI hundreds conventionally arrive between 90 and 110; going above that under chase pressure is rare. Shadab produced what he had never produced before — a maiden ODI century — from a position where sides usually concede.

The insight sits not in the number but in the slot. In international cricket, a No. 8 is often a mislabelled batter — sides treat him as bottom order while he is capable of top-order work. Pakistan's shortage was never batting ability at eight; it was the lateness with which that ability gets identified, and its use as emergency rescue rather than as plan. Shadab's innings is proof of the ability.

The limits of the proof are just as sharp. Turning one innings into a permanent promotion is the exact error I have chased for three decades. His bowling figures are absent from the report, so half his all-round value sits in the dark. And I opened the Centurion spreadsheet again, and the number had not moved. In December 2026 India won that Test, but my false-shot model flagged that the top three had survived on 27 per cent false shots against Kagiso Rabada and Marco Jansen. The win came from somewhere else and we turned it into a batting template. Lahore is the same error running in reverse.

Rauf's seven runs and the wrong definition of depth

Haris Rauf finished 7 not out. He defended, ducked, survived, and eventually hit the winning runs. That is courage, and I am not mocking it. But nobody gets to sell me seven runs at No. 11 as evidence of a batting strategy. Seven runs at eleven is a data point, not a skill certificate.

Here is the line that should come out of this match and will not: depth does not mean your No. 8 and No. 11 can save you; depth means you never need them. A side that needs 88 from the last pair is not deep — it survived the night. Filing the record as a depth certificate is the same muddled logic we heard around Ishan Kishan's Rs 15.25 crore price tag.

And here I distrust my own model, which I will not hide. My par-score and win-probability models give tailenders close to zero weight because historically that is what they are worth. At 154/9 needing 88, my model keeps the win probability in low single digits, and that estimate deserves to be published. So when Shadab did what the model says should not happen, I will not call it a model error. I will say the model cannot measure what sat in Rauf's defence and Shadab's shot selection. I was wrong for eleven months, which is exactly why I trust this now — I know where it breaks.

What happened to xG in football is about to happen to par-score models: people will treat them as verdicts when they are opening bids. One boundary condition, stated plainly, because cricket and football do not map cleanly. Football caps nothing — no side can score beyond the clock, and the clock always ends. Cricket stops counting runs the moment an innings closes or a side is bowled out. So here a par score is a budget, not a probability, and the budget that loses is the one spent early.

Captaincy, workload and a word I do not trust

Shaheen Shah Afridi's 4 for 46 is not a statistic; it is the direction of the match. Breaking the top order with the new ball and holding pressure through the middle is what kept England to 241 and what kept the target at 242. Captain and lead fast bowler in one body is the most expensive role model in the sport.

I will not call him injured, because I do not know. I will say this from forty years of watching: fast bowlers' return timelines are set by press releases now, not calendars. "Week to week" mostly means the injury is nowhere near healed and a shorter word was found for the media. The next fixture is a final. Before a final, a captain-bowler's workload is measured in overs that show up after the twentieth, not in the first ten.

Where I could be wrong

The objection with the most weight first. Losing two or three wickets inside the powerplay on a fresh white ball in Lahore is not automatically a structural crisis. Without ball-by-ball data I cannot separate "chronically fragile top order" from "one bad twenty minutes." My own risk flag says it plainly: over-extrapolating from a single-match sample. If that same top three posts 250 in the final, my structural line comes down and I will write the reversal myself.

Second, the objection against me. I have a habit of claiming the stands, and in Lahore I was not in them. I watched from Delhi on a screen because there was no other route to the match. I am writing it down so nobody later credits me with a close read of the pitch. In 2026 I was in the stands. The model had not been invented yet. Today the model exists and the stands do not. Treating either as a substitute for the other is the model worship my column exists to attack.

Third, and I am pulling this before my producer does. The consensus on this match — that it was a historic, thrilling win and that Shadab's hundred is a big deal — is fully supported by my numbers. An 89-run unbroken stand is the record for the tenth wicket in a successful ODI chase, and that figure will still be standing in twenty years. My objection is not to the record but to the meaning being stuffed into it. When the numbers back the consensus, print that — and here they do, on the record.

Fourth, my model's known failure mode. My par-score logic wants pitch dimensions, dew and first-innings run rate. On this match I have none of the three in verified form. At Eden Gardens in 2026 I ran that model and went live arguing the pitch was a 165 par, not a 180 slog track, when Kolkata Knight Riders collapsed from 118/2 to 149/8. That night the model was right. In Lahore I do not have the model's fuel, so everything here is bracketed and I will not print brackets as verdicts. That is a result too: not every match can be analysed with the same confidence, and saying so is the honesty that separates this column from the rest of the cricket television.

What comes next

I will grade this column, because a prediction I cannot score later is not a prediction, it is a mood.

First, watch Pakistan's top three in the final. If they come through the first ten overs with fewer than two wickets down, I will withdraw the structural-weakness line in the next column and write that Lahore's powerplay was one bad day. If it happens a third time, the question stops being about a final and becomes about the shape of the opening pair.

Second, I will publish Shadab Khan's average and strike rate across his next five ODIs. Above 30 at a strike rate over 90, and the one-innings-outlier line retires. Below it, and I will also write that Lahore's night was the most beautiful thing in cricket — a thing that happened once.

Third, England. If their next ODI innings also ends early with more than eight overs unused, then "being bowled out is the par leak" graduates from bracket to permanent framework. Once is an accident. Three times is a habit, and habits show up in scorecards exactly the way records do — they just never get a highlight package.