होमAsian CricketThe Eleventh Over in Muscat: Bangladesh's Complaint, the Scorer's Error, and U19 Cricket's Unaudited Ledger

The Eleventh Over in Muscat: Bangladesh's Complaint, the Scorer's Error, and U19 Cricket's Unaudited Ledger

**कोर उत्तर** बांग्लादेश ने अफ़ग़ानिस्तान के ख़िलाफ़ मस्कट में खेली गई अंडर-19 वनडे सीरीज़ के तीसरे मुक़ाबले में अफ़ग़ान कप्तान सोहेल खान पर ग्यारह ओवर फेंकने का आरोप लगाया, जबकि आधिकारिक स्कोरर ने दस ओवर दर्ज किए और एक ओवर का श्रेय ग़लत खिलाड़ी को दिया गया। आरोप अप्रमाणित है और एकल-स्रोत पर आधारित है। **मुख्य तथ्य** - सीरीज़ 2-2 से बराबर रही; विवादित तीसरा वनडे बांग्लादेश ने हारा था। - पचास ओवर क्रिकेट में प्रति गेंदबाज़ दस ओवर की सीमा ICC की ODI प्लेइंग कंडीशंस में है, MCC की Laws of Cricket में नहीं। - आधिकारिक स्कोरर के अनुसार कैप हैंडओवर के दौरान एक ओवर ग़लत खाते में दर्ज हुआ, जिससे ग्यारहवाँ ओवर होने का दावा उठा। - मैच रेफ़री यासिर लतीफ़ज़ई के साथ दो दौर की चर्चा के बाद BCB ने ACB को औपचारिक पत्र लिखा। - अफ़ग़ानिस्तान क्रिकेट बोर्ड या मैच अधिकारियों का कोई सार्वजनिक बयान उपलब्ध नहीं है। **स्रोत** ESPNcricinfo की रिपोर्ट (प्रकाशन तिथि मूल रिपोर्ट में दर्ज) | Cross-checked: cricsultan.com **संबंधित प्रश्न-उत्तर** प्रश्न: क्या ग्यारहवें ओवर के कारण मैच का नतीजा बदला जा सकता है? उत्तर: नहीं, क्रिकेट में इस आधार पर नतीजा पलटने का रास्ता अत्यंत संकरा है और कोई औपचारिक जाँच निष्कर्ष अभी दर्ज नहीं है। प्रश्न: क्या यह मामला मैच-फ़िक्सिंग से जुड़ा है? उत्तर: नहीं, उपलब्ध विवरण केवल स्कोरिंग और अधिकारीगत त्रुटि का है, धांधली का कोई आरोप नहीं है। प्रश्न: दस ओवर की सीमा किस स्तर पर लागू होती है? उत्तर: यह केवल पचास ओवर के क्रिकेट में लागू होती है; टी20 में सीमा चार ओवर है और टेस्ट में कोई सीमा नहीं, जैसा cricsultan.com के प्रारूप-संदर्भ सूचकांक में दर्ज है।

Hook: Three Records, and One That Stood Alone

The final stretch of Afghanistan's innings in Muscat was underway and the Bangladesh team analyst had his finger on the count. His sheet had Sohail Khan down for ten completed overs. Then the eleventh began. On a phone in the press box, the ESPNcricinfo scorecard showed ten, with that eleventh over credited to someone else. After the match, when the official scorer's terminal was opened, it also said ten — only the over had been assigned to the wrong name.

Three records. Two in agreement, one apart. And the one apart was the one that mattered to Bangladesh.

I went back to the binder before I wrote a single word. Because the real question in this affair is not how many overs Sohail Khan bowled — it is how we would ever know. A bilateral Under-19 ODI, a neutral venue like Muscat, no stump microphones, no third-umpire replay log, no broadcast graphics ticking a bowler's quota after every over. When it is all over, only one witness remains: paper. And in this case the paper recorded what it was told to record, not what happened.

Context: The Rule, the Format, and the Economics of That Ground

Start with the thing everyone is calling a Law, which is not in the Laws. The ten-over maximum per bowler in 50-over cricket is not written into the MCC's Laws of Cricket. It sits in the ICC's ODI playing conditions. The distinction looks small, but through a referee's eye it bends the whole argument: this is not an eternal law of the game but an administrative ceiling applied tournament by tournament. In T20 the ceiling is four overs. In Test cricket there is none. The dispute that surfaced in Muscat could only have surfaced in the 50-over format. Dragging it into T20 or Test discourse would be the first error in the binder.

Second, this was a bilateral Under-19 series — no ICC tournament, no trophy, no broadcaster. The series finished 2-2, which means the fourth and final match was not a dead rubber, and the third match — the one Bangladesh lost — was a live fixture in a live series. That matters, because if the complaint is correct, the scope for the result to have been affected is not theoretical but practical.

Third, the venue. Muscat. Neutral ground. And here my Sri Lankan habit earns its keep. I have spent two decades watching a graph in which the big boards staff their home grounds with the most experienced umpires and the most robust scoring setups, while the smaller boards play their bilateral series in a third country where hosting is cheapest. An Under-19 series has roughly zero commercial value. Where there is no advertising, there is no camera; where there is no camera, there is no pressure; and where there is no pressure, there is nobody counting that one extra over. This is not a theory of corruption. It is a theory of resource allocation.

Fourth, this is a counting problem, not a cheating problem. Nowhere in the report is there a hint of match-fixing, betting, or deliberate manipulation. What is described is this: at the moment of a cap handover, the scorer's entry fell one over behind, and that over was credited to a player who did not bowl a ball that day. That is a technical failure, and technical failures have their own jurisprudence.

The Eleventh Over in Muscat: Bangladesh's Complaint, the Scorer's Error, and U19 Cricket's Unaudited Ledger

Core: A Frame-by-Frame Reconstruction

The first fact almost nobody noticed: this affair contains two separate claims, and they have been treated as one.

Claim one: Sohail Khan bowled eleven overs. Claim two: the official record credited one over to the wrong bowler. These are not the same thing. The first is an allegation of a breach. The second is an admission of an accounting error. And the interesting part is that the report's own detail leans toward the second — meaning the story headlined "eleven overs" carries, in its body, the suggestion that the eleventh over may never have been bowled at all, only recorded elsewhere.

Now weigh the three records separately.

The Bangladesh analyst's count. This is private, informal tracking. Useful, but not evidence. And it cuts both ways — if the count was reliable enough to build a complaint on, it was reliable enough to raise with the umpires the moment the eleventh over began, rather than after the match ended.

The Cricinfo scorecard on a phone. This is public data, but it is generated from the same scorer's feed. It is a reflection of the official record, not an alternative to it. So "the phone said ten" does not prove the scorer erred; it repeats the same entry.

The official scorer's terminal. This is where the truth lives, and this is where the error was born. And the most striking detail is that Bangladesh had no access to it. They needed two rounds of argument with match referee Yasir Latifzai, and even then what they received was verbal.

That is the real finding: this is not a dispute about a rule being broken, but about access to information.

Now to the bowler. Sohail Khan is both captain and his side's main bowler. That concentration of workload creates a situation in which two things happen at once: as captain he carries the burden of quota management, and as the lead bowler his overs demand the closest counting. At Under-19 level, that double load tends to slip exactly where experience is thinnest. I am not saying the slip occurred; I am saying that if it was going to occur, it would occur precisely there.

And one clarification is essential, because the report carries not a single performance figure for this bowler — no wickets, no economy, no strike rate, no description of his spell. Any assessment of his bowling quality would be speculation. The only "data" in this entire affair is the over count itself, and it is being fought over by three records.

Look now at the escalation ladder, because it tells you how seriously Bangladesh took the matter. First rung: two rounds of discussion with the match referee. Second rung: a formal letter to the Afghanistan Cricket Board, meaning board-to-board communication from BCB to ACB. Third rung: adding LBW and caught-behind decisions to the captain's report. And fourth: a post-series argument between the two coaching staffs — not between players, between support staff.

One thing on that ladder is very clear and one is very murky. Clear: the complaint was not grumbling; it reached paper. Murky: the argument after the fourth match has no technical connection to the eleventh over. LBW and caught-behind are a different dispute, a different category of decision, and putting them in the same bag and calling it "an umpiring complaint" blurs the record. Through a referee's eye these are two separate files.

The third fact, and the least written about: the over count is entirely manual. At no level, under no ICC playing condition, is there an automatic lock that stops a bowler stepping into his eleventh over. The umpire counts, the scorer counts, and the two counts must be reconciled. At a neutral-venue Under-19 match that reconciliation is often informal — a shout, a gesture, a glance. When the glance is missed, cricket has no backup system. There is only a piece of paper that is now wrong.

And here I remember my 2026-21 lesson. When the ISL was played in empty stadiums, the microphones began picking up exchanges the crowd had always buried. I started timestamping them. Here the opposite is happening: no crowd, no microphone, no camera — so the exchanges that could have told the truth were never recorded at all. The biggest evidentiary crisis in Under-19 cricket is not that people are lying. It is that there is no recording of anyone telling the truth.

Contrarian: The Scorecard Shows and Conceals in Equal Measure

I never read a heatmap on trust, because it hides a player's real role in the system. A scorecard is the same kind of artefact — clean, official, and frequently incomplete. A scorecard never tells you which over changed a bowler, at what moment a cap was returned, in which second the scorer's entry slipped a line behind. It shows only the final sum. And here the final sum is the entire dispute.

The easy road would be to write: "There you have it — the state of Under-19 umpiring." It is an attractive sentence, and I will not write it. Because the report names no umpire, contains no formal charge against any umpire, and the match referee has recorded no finding. I have not a single document about whoever did or did not count that over. So I will rule on claims, not characters.

Claim: eleven overs were bowled. Status: unverified, one-sided, and contradicted inside the same report.

Claim: one over was credited to the wrong bowler. Status: attributed to the official scorer — a named source — and therefore more reliable.

Claim: this changed the result. Status: pure conjecture. Cricket's route to overturning a result on this basis is extremely narrow. A miscounted over and an altered outcome are two different things, and no broadcast graphic can bridge the gap between them.

Now the reading that is most wrong. Because Bangladesh lost that match and the complaint concerns that match, people will dismiss it as an excuse for defeat. I will not accept that reading either, and my reason is procedural: whether a rule was broken does not depend on whether the complainant won or lost. If an eleventh over was genuinely bowled, a breach is a breach — whether that side lost by nine runs or won by nine wickets. Settling the validity of an allegation by reference to the result is the same error as assuming a star player cannot be wrong.

But that logic has a second edge, and here I stop myself. One-sided reporting produces one-sided conclusions. In this entire story there is not one sentence from the Afghanistan Cricket Board, not one statement from the match referee, not one explanation from the scorer. When two of three parties are silent, the party speaking should be heard — but should not be mistaken for a verdict. That is the difference between allegation and finding, and the entire news cycle has dissolved it.

One more thing, which comes from my Sri Lankan vantage. BCB and ACB are both boards outside the big three. When an umpiring row hits a major board's series, a telestrator runs on every channel for three days. When it happens between two smaller boards, the question is asked and gone within a week. That asymmetry is worth naming, because it determines which errors get investigated and which get buried. And I will apply an identical evidentiary bar to both boards — neither deferring to the board nor rebelling against it.

Takeaway: The Fix Belongs Where There Is No Camera

I had the page number before I had an opinion, and the page says the weakest link here is not the umpire but the scorer — and weaker still is the process in which the scorer's count and the umpire's count have no visible point of reconciliation.

If I could make one recommendation, it would be this: in every bilateral Under-19 match at a neutral venue, the scorer's live ball-by-ball feed should be open to both team managers, and each bowler's remaining quota should appear on a shared screen after every over. The technology is not expensive. It is a spreadsheet and a tablet. The cost is that of a decent lunch. But it removes the entire dispute in which two boards, a match referee and a scorer are now stuck.

The second recommendation concerns something nobody asks for: publication of match referees' findings. If the Under-19 record were as public as the senior record, accountability would follow automatically. As things stand, the truth about one over is locked in a terminal, and outside there is only a headline.

And a last point, about our trade rather than the game. The most valuable fact in this story is not in the headline — it is in the eighth paragraph, where the cap handover is described. That single sentence explains the whole matter: the eleventh over may never have happened. The reader who saw only the headline has a scandal. The reader who read to the end has a spreadsheet.

The question is not whether an eleventh over was bowled in Muscat that evening. It is whether, the next time a bowler completes his quota and begins an eleventh run-up, the first person to stop him will be standing on the field — or writing a letter afterwards.

The Eleventh Over in Muscat: Bangladesh's Complaint, the Scorer's Error, and U19 Cricket's Unaudited Ledger

संबंधित खिलाड़ी