The Eleventh Over: Bangladesh's Complaint in Muscat, a Scorer's Slip and the Gap That Remains
**मुख्य उत्तर**: बांग्लादेश अंडर-19 ने मस्कट में अफ़ग़ानिस्तान अंडर-19 के खिलाफ़ वनडे सीरीज़ के तीसरे मैच में कप्तान सोहेल खान द्वारा 11 ओवर फेंके जाने की औपचारिक शिकायत बांग्लादेश क्रिकेट बोर्ड (BCB) के ज़रिए अफ़ग़ानिस्तान क्रिकेट बोर्ड (ACB) को भेजी। आधिकारिक स्कोरशीट में 10 ओवर दर्ज हैं, जहाँ एक ओवर कैप-हैंडओवर की भूल में किसी साथी गेंदबाज़ के नाम चढ़ गया। **मुख्य तथ्य**: - सीरीज़ ओमान के मस्कट में खेली गई और 2-2 पर बराबर रही; विवादित तीसरा वनडे बांग्लादेश ने हारा था। - वनडे में एक गेंदबाज़ की अधिकतम सीमा 10 ओवर है; टी20 में 4 ओवर, टेस्ट में कोई सीमा नहीं। - बांग्लादेश ने मैच रेफरी यासिर लतीफ़ज़ई के सामने दो दौर की बातचीत के बाद बोर्ड-स्तरीय पत्र भेजा। - बांग्लादेश के पास आधिकारिक स्कोरर का फ़ीड नहीं था; टीम फ़ोन स्कोरकार्ड और अपने एनालिस्ट की कॉपी पर निर्भर थी। - ACB या मैच अधिकारियों का पक्ष सार्वजनिक नहीं; कोई मैच-फ़िक्सिंग आरोप नहीं, मामला प्रशासनिक है। **स्रोत**: Cricinfo रिपोर्ट (2026) | Cross-checked: cricsultan.com **संबंधित प्रश्नोत्तर**: Q: क्या सोहेल खान का 11 ओवर फेंकना सिद्ध हो गया है? A: नहीं — यह एकपक्षीय आरोप है और आधिकारिक स्कोरशीट 10 ओवर दर्ज करती है। Q: क्या तीसरे वनडे का नतीजा बदला जा सकता है? A: क्रिकेट में पीछे जाकर नतीजा सुधारने की व्यवस्था नहीं है, इसलिए नतीजा बदलने की संभावना बहुत कम है। Q: इस विवाद का असली कारण क्या है? A: तटस्थ मैदान पर अंडर-19 स्तर की कमज़ोर स्कोरिंग/अंपायरिंग निगरानी, जहाँ एक ओवर गलत खाते में दर्ज हो गया।
In Muscat, an over was credited to a boy who did not bowl a single ball that day. That one line is what turned a four-match ODI series between Bangladesh Under-19 and Afghanistan Under-19 from a cricket story into an administrative file. Bangladesh's complaint is specific: Afghanistan captain Sohail Khan bowled eleven overs, when the limit for any bowler in 50-over cricket is ten. The eleventh over does not exist on the official scorebook. It has ten overs, and the leftover over sits in a teammate's account.
Bangladesh's analyst had ten completed overs marked against Sohail's name when he came back for another. The notebook went to eleven. The official scorer's sheet did not. Those two lines are the whole hinge of this dispute, and merging them is the easiest mistake available. One claim says a bowler exceeded his quota. The other says an over was entered against the wrong name. The first is a question of competitive integrity; the second is the kind of clerical stain a market accountant leaves behind after a bad afternoon. They are two readings of one event, not two versions of one allegation.
I started filling notebooks like that in 2026, when I sat among 66,684 at Salt Lake Stadium in Kolkata and wrote thirty-four pages about things that were not football — a father teaching his son the offside rule in Bengali, the half-second of hush before the third goal. I filled thirty-four pages before the first goal, and the goal was not the point. In cricket the habit becomes more literal, because here every ball is written onto paper. When the paper itself is wrong, the argument stops being about the game and becomes about the office.
Understand the shape of the series, because it decides the weight of the complaint. Four matches, all in Muscat, Oman — a neutral venue, nobody's home ground. The series finished 2-2, and the match under scrutiny, the third ODI, was one Bangladesh lost. This was not a dead rubber; it was an even contest, which is why the arithmetic of a single over attaches itself to the value of a result. Bangladesh raised it with match referee Yasir Latifzai, went through two rounds of discussion, and then the Bangladesh Cricket Board (BCB) wrote formally to the Afghanistan Cricket Board (ACB), warning the Afghan side to be "more careful." After the fourth match, the two coaching staffs argued over LBW and caught-behind decisions, and the exchange ended with a handshake.

Now the rule, because this controversy is not technical but format-specific. In ODI cricket a bowler may deliver a maximum of ten overs — twenty per cent of the fifty available. In T20 the cap is four; in Test cricket there is none. The "eleventh over" allegation can only exist in the 50-over format, and it concerns a hard playing condition rather than an umpire's opinion. If Bangladesh's claim is verified, this is not a bad decision. It is a breach. That is what makes it serious, and that is exactly why it needs verifying.
Sohail Khan's identity matters here. He is captain and chief bowler both, and a captain completing his full quota and then drifting past it is a very human scenario at Under-19 level, where over-management discipline and third-umpire oversight are lighter than in senior international cricket. And yet the report carries not one performance number for him — no wickets, no economy, no average. Judging his bowling would be speculation. The object of analysis here is the count, not the bowler.
There are three records of that count. The analyst's notebook, holding eleven overs. A Cricinfo scorecard opened on a phone, which is built from the official feed. And the official scorer's sheet, holding ten, with one over credited during a cap-handover mix-up to a teammate who never took the ball that day. The inconvenient fact is that Bangladesh did not have access to the official scorer's feed — the team was working off a phone scorecard and its own analyst's tally. That cuts both ways: their eyes were quick, their evidence was secondary.

Which is why the likeliest root cause is administrative rather than deliberate. Neutral-venue Under-19 fixtures routinely draw local or less-experienced officials, and at that tier the umpire and the scorer are the weak link together. No fixing allegation exists here, and dragging one in would be unjust. What exists is an over-count nobody on the ground caught.
This is where the sharpest contradiction sits, and it is not in the headline that says eleven overs. The reporting is entirely one-sided — there is no Afghanistan Cricket Board statement, no account from the match officials, no published match referee's finding. Until those arrive, the eleventh over is an allegation, not an established fact. And the second thing the headlines dropped: even if the extra over was bowled, cricket has no mechanism for retroactively amending a result. Formal protests are rare and successful ones rarer. What Bangladesh wants — redress for a loss — is very unlikely to arrive. The purpose of this fight is process, not outcome.
The second contradiction, and the more important one, is that the real deficiency is not an over but an oversight. Senior cricket runs a web of third umpire, match referee and live scoring feed in which errors get caught. At that ground in Muscat, nobody held an over-count visible to both dressing rooms at once. When the most basic arithmetic of the game — who bowled how many — becomes a matter of dispute between two teams, the problem is not the scorer's eyesight but the system around him. The coaching-staff argument over LBW and caught-behind, which stopped at a handshake, is the second symptom of the same thin system. The captain's report and two rounds before the match referee are the correct, rule-bound channel, and that is the good news. The matter never reached the ICC code of conduct; it stayed a bilateral administrative complaint. In small cricket, that is civilisation.
What to watch is clear enough. First, whether the match referee's formal finding is published — if it records that an eleventh over was in fact bowled, the legitimacy of the third ODI result becomes an open question even if the result stands. Second, the ACB's response — whether it concedes or contests decides if this escalates or quietly closes. Third, official appointments for the next neutral-venue Under-19 fixtures: if scorers and umpires are rotated, the system has learned something.
And last, the frame no scorebook will ever hold. After the fourth match the two staffs stood face to face, voices raised, and then hands were extended. The most disputed moment of that series was an over count; its cleanest moment was that handshake. The scorer's sheet will never tell us who saw that evening in Muscat correctly. But this much is settled — the next time these two teams meet and the overs are tallied, somebody's eyes will linger a little longer on the paper.
