Shadab Khan's 113, Haris Rauf's 19 Balls and Pakistan's One-Wicket Win: The Real Data Behind the Lahore Thriller
कोर उत्तर: रिपोर्ट के अनुसार पाकिस्तान ने लक्ष्य 242 का पीछा करते हुए 242/9 बनाया और एक विकेट से जीता; 242 के लक्ष्य पर 242/9 अंकगणितीय रूप से टाई होता है, इसलिए आधिकारिक स्कोरकार्ड से पुष्टि जरूरी है। मुख्य तथ्य: - शादाब खान ने 96 गेंदों पर 113 रन बनाए; स्ट्राइक रेट 117.7 रहा। - शादाब खान के 113 रनों में 82 रन बाउंड्री से आए: 13 चौके और 5 छक्के। - हारिस रफ ने 19 गेंदों पर 7 रन बनाए; दसवें विकेट की 89 रन की साझेदारी हुई। - नासीर हुसैन ने कहा कि इंग्लैंड दबाव में बिखरा और उसे पिछले मैच से सबक लेना चाहिए था। - पाकिस्तान ने त्रिकोणीय सीरीज़ के फाइनल में जगह बनाई; मैच लाहौर के गद्दाफी स्टेडियम में खेला गया। स्रोत: उपलब्ध मैच रिपोर्ट और स्टेज-2 विश्लेषण; प्रकाशन तिथि और वर्ष मूल सामग्री में नहीं दिए गए। CricSultan (cricsultan.com) डेटाबेस से स्वतंत्र सत्यापन नहीं हुआ। संबंधित प्रश्न-उत्तर: प्रश्न: पाकिस्तान की जीत का सबसे बड़ा डेटा पॉइंट क्या था? उत्तर: हारिस रफ की 19 गेंदें, क्योंकि उन्होंने शादाब खान को समय दिया और उनकी सर्वाइवल वैल्यू 7 रन से अधिक थी। प्रश्न: क्या शादाब खान की 113 रन की पारी स्थायी बल्लेबाजी उभार का सबूत है? उत्तर: नहीं; यह उनके करियर बेसलाइन से बाहर की पारी है और 72.6 प्रतिशत रन बाउंड्री पर निर्भर थे। प्रश्न: इंग्लैंड के लिए असली चिंता क्या है? उत्तर: नासीर हुसैन के अनुसार इंग्लैंड की क्लोजिंग-आउट क्षमता दबाव में बार-बार ढही; यह पैटर्न एक मैच से आगे का संकेत है।
The scorecard was still warm
“The scorecard was still warm when we hit record.” At Gaddafi Stadium, Lahore, Pakistan chased 242 and finished on 242/9 to win by one wicket. Shadab Khan made 113 off 96 balls. Haris Rauf faced 19 balls for 7 runs. The tenth wicket added 89. Social feeds filled with reactions from Shai Hope, Daren Sammy, Angelo Mathews, Ian Bishop and Nasser Hussain. Someone called it “Absolute Cinema.” Someone else reached for Pakistan’s “clutch gene.” Hussain talked about England crumbling under pressure.
My first reaction looked like the feed. Then I opened the scorecard. Two things stood out. Pakistan had won after their top order failed. England had lost in a way that looked familiar. The clutch-gene reading collapses under the arithmetic. This was a tail event built on one outlier innings and one act of survival, and it exposed England’s repeated closing-out weakness. Three numbers carry the argument: 153/9, 89 and 19.
The context
This was the fourth match of an ODI tri-series, a league fixture with direct final-qualification consequence. Pakistan hosted England at Gaddafi Stadium, Lahore. The report gives no year, no tournament name, no third team, no toss, no pitch report, no over-by-over scorecard and no bowling figures. That is a serious reporting gap for a match that settled a finalist. “The press box taught me that silence can be a headline.” Here the scorecard’s silence is the headline.

Pakistan’s top order stumbled early: Fakhar Zaman, Saim Ayub and Babar Azam were among the early dismissals. That is the cohort on which Pakistan’s ODI scoring model depends. Shadab produced a maiden ODI century. Haris Rauf, a specialist fast bowler and a genuine No. 11, survived 19 balls. Hussain said England crumbled when put under pressure at the end. He also said England should have learned from the last game. The second sentence matters more. It turns a one-off into a pattern signal.
Gaddafi Stadium has historically been a high-scoring venue. If this was a day-night match, a total of 241 or 242 would look below par. The material gives no pitch report, no dew information and no start time. I will not call it under-par as fact. What can be said is this: England produced a total Pakistan could chase, and Pakistan needed nine wickets to get there. That combination is the story.
The ODI template has three acts: powerplay, middle-overs squeeze, final-10 acceleration. The report gives no over numbers, so phase attribution can only be inferred from wicket sequencing. The top order fell early, which means Pakistan were behind in the early phase. The last pair won the match, which means Pakistan won the death phase. What happened in the middle overs is unavailable.
Core: the arithmetic of 89
A correction comes first. The report gives Pakistan 242/9 and a target of 242. In cricket arithmetic, 242/9 chasing 242 is a tie. Either England finished on 241, or Pakistan reached 243/9. The 89-run tenth-wicket stand and the 153/9 starting point fit the 242/9 version. My first inference is that England finished on 241 and the target was 242. An official scorecard must confirm it. This small inconsistency matters because the entire one-wicket narrative sits on a one-run boundary. If one line of the score is wrong, the whole clutch story is standing on a one-run question mark.
Now the real arithmetic. Pakistan finished on 242/9. The tenth wicket added 89. That means Pakistan were roughly 153/9 when the last partnership began, needing 89 to win. Shadab scored 82 of those runs. Rauf scored 7. The sum is 89, which leaves zero extras in the partnership. A 89-run last-wicket stand with zero extras means England did not take the wicket, and England’s mistakes did not leak runs either. Under pressure, England became tight, not smart. That is the hardest evidence for Hussain’s “crumbled” line.
Shadab’s innings: 113 off 96, a strike rate of 117.7, with 13 fours and 5 sixes. That is 82 runs from boundaries, 72.6 percent of his total. A typical ODI century has a boundary share closer to 50-62 percent. Shadab did not rotate strike; he punished. That explains the strike rate. It also exposes the risk. A 72.6 percent boundary-dependent innings is a high-variance innings. Against better death bowling, the same approach can turn 113 into 45. This is not a criticism of the player. It is the risk math of the innings.
Shadab’s career baseline sits far below this innings. Available benchmarks put his ODI average in the mid-20s and his strike rate around 85, pending independent verification. The direction is clear: this innings sits outside his own distribution. A leg-spinning all-rounder producing a maiden ODI hundred at 117.7 is a low-frequency event. The correct read is that he has the ball-striking ceiling to do this occasionally. The wrong read is that he has become a reliable ODI match-winner with the bat. Shadab is a bowling all-rounder whose batting is a bonus. Upgrading his batting role on the basis of this innings is a category error.
There is a workload flag. Shadab has a soft-tissue history involving hamstring and thigh issues, pending verification. A 96-ball innings plus a full spin workload is the dual-load profile that precedes soft-tissue trouble in all-rounders. This is a flag, not a prediction.
Haris Rauf: 7 off 19, a strike rate of 36.8. In the scorebook, that is a minor line. In the match arithmetic, it is the biggest line. A No. 11 surviving 19 balls is a survival event, not a scoring event. Those 19 balls bought Shadab the overs he needed to reach 113. In win-probability terms, those 19 balls were worth far more than 7 runs. Hussain and Bishop both highlighted Rauf, and they were right. Reading Rauf’s 19 balls as evidence of batting skill is the same mistake as reading Shadab’s 113 as a permanent batting upgrade. Rauf is a specialist bowler whose batting is a liability that happened not to cost Pakistan on this occasion.
The strategic point is that Pakistan won despite their batting system, not because of it. Fakhar, Saim Ayub and Babar are the three names on which Pakistan’s ODI scoring model depends. They fell early. A side at 153/9 chasing 242 has a top-order structural problem. The result is a tail event, not a repeatable template. Any standard win-probability model would place a 153/9 chase in the low single digits. Calling this a “Pakistani clutch gene” is the easiest and least accurate route through the data.

England’s failure is more diagnostic than Pakistan’s success. Pakistan needed an outlier individual innings. England needed only their existing closing-out weakness to recur. Hussain said: “When England were put under pressure here at the end, they crumbled.” He also said: “they should have learned it from the last game.” Read the two sentences together. The first is an event. The second is a pattern. A team that does not learn from the last game repeats the same mistake in the next one. England’s problem sits in their death bowling and fielding under pressure, not their batting. Hussain’s framing points there.
The reaction economy deserves its own note. Five international figures, five quote cards. Sammy is a current head coach, so his praise carries professional weight, not neutral-fan weight. Bishop and Hussain are broadcasters and former players. Hope and Mathews are active players. Their reactions describe the mood of the match, not its data. “Absolute Cinema” is clip-able. Clip-able and correct are different things. ODI cricket needs the clip. Analysis needs the scorecard.
One data point is missing: Shadab’s bowling. An all-rounder cannot be assessed on batting alone. How many overs did he bowl, how many wickets did he take, how many runs did he concede? None of it is in the report. England’s bowling figures are missing too. Who conceded, who missed the yorker, who bowled the last over? Without those answers, Hussain’s “crumbled” line is a direction, not a proof.
The report also says nothing about Pakistan’s bowling. A chase-centred report would usually mention a bowling collapse if one had occurred. The likely inference is that Pakistan’s bowlers restricted England to 241 or 242. The inference is not evidence. I will keep it labelled as an inference.
Lahore’s home crowd is a real factor. Pakistan at home in subcontinental conditions have historically been a stronger proposition. England in subcontinental ODI conditions have been weaker since the 2026 cycle. This match was played on that axis. Home advantage does not explain 153/9. It only changes the pressure in which 153/9 was made.
Contrarian: where I could be wrong
The weakest part of my thesis is the word outlier. Shadab’s batting position is not stated. If he batted at 5 or 6 and rebuilt the innings after the top order fell, this was a middle-order rebuild, not a tail-end blitz. Hussain described a “change of intent.” Intent is tactical, not technical, and it can be coached and repeated. If Shadab bats 5 or 6 in the final and produces 40-plus off 40-plus balls, my outlier frame weakens.
England’s “crumble” may also be a selection artefact. If England are rotating their attack in this tri-series, Hussain’s “learn from the last game” line points to experimentation, not first-choice weakness. In that case, the loss says more about personnel than system.
The pitch matters. If Lahore was two-paced or turning, 241 or 242 was par. Pakistan’s top order then fell to conditions, not structural pressure. Without a pitch report, half of my structural concern disappears.
Rauf’s 19 balls could be luck. England may have bowled to him without a plan, missed yorkers, or dropped a chance. No drop-catch or DRS information is available. If luck played a large part in Rauf’s survival, calling those 19 balls skill is premature. “I trust the hot take only after the replay.” Here the replay is missing. The scorecard is all we have.
Takeaway: the final is the real test
Pakistan have qualified for the final. The result is being framed as a boost before the title clash. For me, the final is the test. Watch Pakistan’s top order. If they fall to 60/3 or 80/3 again and the lower order rescues them, the structural concern holds. If the top order bats 50 overs, my concern weakens.
My Shadab test is simple. If his next five ODI innings produce a boundary share above 65 percent and an average below 30, the 113 was a great night, not a new role. If his strike rotation improves and he strings together 40-plus scores at 5 or 6, my outlier frame was wrong. England’s test is their next close match: can they save 30 runs in the last 10 overs, or do they crumble again?
The question is whether we are watching the first chapter of a new Shadab career, or one unforgettable night that is easy to clip and hard to repeat. The best analysis starts where the highlight reel stops. For me, that place begins at 153/9, 89 and 19 balls — after the clip, inside the scorecard.
