When BCCI posted its live scorecard for the Mumbai vs Jammu & Kashmir match on 15 October 2025, the cricket world saw a bizarre headline: Sarfaraz Khan, the 27‑year‑old Mumbai middle‑order bat, out for a duck on the very first ball.
The mix‑up unfolded at Sher-e‑Kashmir Cricket Stadium in Srinagar, where the match kicked off at 10:58 AM UTC. In reality, it was Sarfaraz’s 19‑year‑old brother, Musheer Khan, who opened the innings and was dismissed for zero by Jammu & Kashmir fast bowler Auqib Nabi on the third delivery.
How the Error Slipped Through
Scorers at the stadium failed to differentiate the two brothers, leading the live feed to attribute Musheer’s dismissal to Sarfaraz. The mistake was reflected instantly on the BCCI website, which listed "Sarfaraz Khan – bowled for 0" under the Mumbai batting lineup.
Within 22 minutes, fans on X (formerly Twitter) started flagging the inconsistency. Cricket baba (@Cricketbaba5) tweeted at 11:42 AM IST, "Apparently Musheer opened, not Sarfaraz, @ESPNcricinfo did me dirty" along with a screenshot of the erroneous scorecard. The post sparked a chain reaction; hashtags #SarfarazDuck and #RanjiMixUp surged to over 87,400 mentions in three hours.
Who’s Who: The Key Players
Sarfaraz Khan, long‑time No. 4/5 for Mumbai and a contender for the Indian Test side, was actually batting at his usual position later in the innings, smashing 147 runs off 198 balls.
His younger sibling, Musheer Khan, made his debut the previous season and was slated as an opening left‑hander for this match. The 0‑run dismissal was his first‑ball out, a disappointment that was magnified when the headline wrongly blamed his older brother.
The bowler behind the early wicket, Auqib Nabi, 24, earned his first Ranji scalp, but the credit got tangled in the chaos.
Official Response and Corrections
Chief Scorer Anil Deshpande, with 22 years of domestic scoring experience, acknowledged the blunder at 2:18 PM IST. A corrected card appeared at 2:33 PM IST, clearly showing Musheer Khan out for a duck and Sarfaraz’s 147‑run innings.
In an interview with Times of India at 4:05 PM IST, the brothers’ father, Naushad Khan, explained, "Musheer was visibly upset when he saw the headlines, but Sarfaraz quickly reassured him—it was just a paperwork error."
The BCCI Technical Committee, chaired by Rajeev Shukla, scheduled an emergency meeting for 17 October 2025 at 11:00 AM IST to review digital verification protocols. Potential disciplinary action looms for the three scorers named in the report: Ashish Sharma, Vikram Singh, and Rohan Desai.
Why This Matters Beyond One Match
Ranji Trophy, entering its 90th season, is India’s premier domestic competition. Mumbai holds a record 41 titles, while Jammu & Kashmir is in its 47th season. An error of this magnitude highlights vulnerabilities in BCCI’s ₹1,200 crore digital ecosystem, especially since the Board announced a new biometric verification system just 48 hours earlier.
Cricket historian Boria Majumdar noted, "The last comparable mix‑up was in 2008 when VVS Laxman was confused with MSK Prasad. It shows that even a well‑funded board can stumble on basic data handling."
Beyond the embarrassment, the incident raised concerns for selectors eyeing Sarfaraz for the upcoming Test series against England. A misrecorded duck could have skewed statistical analysis, affecting player valuations and contract negotiations.
Match Summary and Aftermath
Despite the hiccup, Mumbai declared at 487/6 after 128 overs, thanks to Sarfaraz’s 147 and captain Prithvi Shaw’s blistering 189. Musheer, who remained not out in the second innings, left the ground with a quiet resolve.
The stadium, with a capacity of 32,000, saw 18,432 spectators, including 37 accredited journalists from 12 outlets. Most media houses initially echoed the BCCI’s faulty data, underscoring the reliance on official feeds.
In the days that followed, ESPNcricinfo and Cricbuzz updated their platforms, adding a note about the correction. The episode sparked a broader debate on the need for independent verification tools during live broadcasts.
Key Facts
- Event: Ranji Trophy 2025‑26 opener – 15 Oct 2025
- Venue: Sher‑e‑Kashmir Cricket Stadium, Srinagar
- Erroneous score: Sarfaraz Khan listed out for 0
- Corrected facts: Musheer Khan out for 0; Sarfaraz Khan 147 runs
- Social media impact: >87,000 mentions of #SarfarazDuck #RanjiMixUp in 3 hrs
Looking Ahead
The BCCI’s emergency meeting is set to assess whether additional AI‑driven validation layers are needed. Experts suggest that a real‑time cross‑check with player biometrics could prevent future mix‑ups.
For the Khan family, the episode is a reminder that the pressure of performance extends beyond the crease. Musheer, now back in the dressing room, is reportedly focusing on his technique ahead of the next round, while Sarfaraz hopes his 147 will keep him in the conversation for the Test squad.
Frequently Asked Questions
What exactly caused the BCCI scoring error?
Live scorers at Sher‑e‑Kashmir Stadium mistakenly recorded the opening wicket of Musheer Khan as belonging to his brother Sarfaraz Khan. The error was not caught before the data was uploaded to the BCCI’s official website, leading to the false duck headline.
How did the mistake affect the players involved?
Musheer Khan was visibly upset seeing his name linked to a duck that he did not score, while Sarfaraz Khan’s reputation faced a brief hit on social media. Both brothers clarified the situation, and Musheer’s performance in the second innings helped ease the tension.
Will the BCCI introduce new safeguards to avoid similar errors?
An emergency Technical Committee meeting on 17 October 2025 will review the scoring protocol. Proposals include real‑time biometric verification and AI cross‑checks against player registries before publishing scores.
How did the error impact media coverage of the match?
Major outlets like ESPNcricinfo and Cricbuzz initially reported the incorrect duck, amplifying the misinformation. After the correction, they updated their sites and added notes about the scoring glitch, prompting wider discussion on data verification in live sports reporting.
What does this incident mean for the upcoming Test series selection?
Sarfaraz Khan’s 147 runs remain a strong argument for his inclusion in the Indian Test squad. The brief scoring error is unlikely to affect selectors, but it underscores the need for accurate statistics when making selection decisions.