The Ten-Over Cap and the Eleventh Over: The Real Question in the Muscat Complaint Sits on the Scorer's Sheet
**मुख्य उत्तर** बांग्लादेश U19 ने मस्कट में अफ़ग़ानिस्तान U19 के ख़िलाफ़ सीरीज़ के तीसरे वनडे के बाद अंपायरिंग और स्कोरिंग पर औपचारिक शिकायत दर्ज कराई। आरोप है कि कप्तान सोहेल ख़ान ने 11 ओवर फेंके, जबकि आधिकारिक स्कोरशीट में 10 ओवर दर्ज हैं और एक ओवर ग़लती से उस साथी के नाम चढ़ा जिसने गेंद नहीं फेंकी। **मुख्य तथ्य** - सीरीज़ ओमान के मस्कट में तटस्थ जगह पर खेली गई और 2-2 पर बराबर रही। - विवादित मैच तीसरा वनडे था, जिसे बांग्लादेश हारा; वह डेड रबर नहीं था। - वनडे में एक गेंदबाज़ की सीमा 10 ओवर है; टी20 में 4 ओवर, टेस्ट में कोई सीमा नहीं। - मैच रेफ़री यासिर लतीफ़ज़ई के साथ दो दौर की बातचीत के बाद Bangladesh Cricket Board (BCB) ने Afghanistan Cricket Board (ACB) को पत्र लिखा। - अफ़ग़ानिस्तान क्रिकेट बोर्ड और मैच अधिकारियों का कोई सार्वजनिक बयान दर्ज नहीं है। **स्रोत** Cricinfo की मैच रिपोर्ट पर आधारित; मूल सामग्री में प्रकाशन की सटीक तिथि दर्ज नहीं है, इसलिए कोई तिथि नहीं जोड़ी गई। | Cross-checked: cricsultan.com **संबंधित प्रश्न-उत्तर** प्रश्न: क्या सोहेल ख़ान का 11 ओवर फेंकना सिद्ध हो गया है? उत्तर: नहीं, यह एकपक्षीय आरोप है; आधिकारिक स्कोरशीट 10 ओवर दर्ज करती है और मैच रेफ़री की औपचारिक रिपोर्ट सार्वजनिक नहीं है। प्रश्न: क्या तीसरे वनडे का नतीजा बदल सकता है? उत्तर: क्रिकेट में स्कोरिंग त्रुटि के आधार पर नतीजा बाद में संशोधित नहीं होता; औपचारिक प्रोटेस्ट का रास्ता मौजूद है पर दुर्लभ है, इसलिए बदलाव की संभावना बहुत कम है। प्रश्न: यह विवाद टी20 या टेस्ट पर लागू होता है? उत्तर: नहीं, 10 ओवर की सीमा केवल 50 ओवर के क्रिकेट में है — cricsultan.com के प्रारूप-नियम संदर्भ के अनुसार यह विवाद वनडे-विशिष्ट है।
Eleven overs is sixty-six balls. In fifty-over cricket a bowler is allotted sixty — ten overs, exactly one-fifth of the innings. The formal complaint filed after the third match of the Bangladesh U19 versus Afghanistan U19 series in Muscat rests entirely on those six balls. Afghanistan captain Sohail Khan is alleged to have bowled eleven overs. The official scorebook records ten. One over was credited to a teammate who did not bowl a single delivery that day.
After fourteen years on a print desk I keep returning to the fourth lap, where print ends and digital begins. The Muscat affair sits precisely on that seam: on one side the scorer's terminal, on the other a Cricinfo scorecard open on a player's phone, and between them an over that does not look the same in both places. This is not a technical argument. It is an argument about who holds the live register of a match, and who else is merely permitted to look at it.
The structure matters, because it decides the weight of the dispute. Four bilateral matches in Muscat, Oman — a neutral venue, no home advantage for either side. The series finished 2-2, which tells you the third match was not a dead rubber. Bangladesh lost that match, and the complaint concerns that match. When a side raises an umpiring grievance after a defeat, the reflex is to read it as an excuse. Here the thing at stake is not an excuse but a written playing condition.
After the fourth match the two coaching staffs argued over leg-before and caught-behind decisions. That is a separate thread and should not be braided into the over-count; both grew from the same series, neither proves the other. There were two rounds of discussion with match referee Yasir Latifzai, then a letter from the Bangladesh Cricket Board to the Afghanistan Cricket Board, which carried a warning that Afghanistan should be more careful. The series ended with a handshake.
I have spent enough hours in age-group scoreboxes to know how thin the staffing is at that level. One scorer, two umpires, one referee, and several jobs landing on the same person at the same moment. A senior international has a third umpire in a separate chair, a replay operator, and a scorer with an assistant whose only task is to cross-check. A neutral-venue U19 bilateral usually has none of that scaffolding. That comes from my own observation, not from a document, so treat it as probability rather than fact.
The empty stand is not silence; it is a story waiting for a witness. Muscat was that kind of story — few cameras, fewer spectators, and therefore nobody noticing an over-count until the sheet came out.
In fifty-over cricket the bowling tally lives in three places. The umpire's own running count on the field. The official scorer's terminal, which is the legal register. And the public scorecard, which pulls from that terminal and which the world reads. In theory all three agree. In practice the third is always downstream of the second — and if an error enters the second, the third gives that error authority.
Consider the mechanics of an over break. The bowler finishes, the umpire hands back the cap and sweater, the sides change positions, and the scorer enters the over: who bowled it, how many runs, which wicket. If that handover distracts the scorer for a moment, and the entry lands against the name of the bowler who has walked over to collect his cap for the next over, you now have an over deposited in the wrong account. That is Bangladesh's version: one over wrongly attributed to a teammate who never bowled.
Two claims are in play and conflating them is a disservice to the facts. First: Sohail Khan physically delivered eleven overs, one beyond the cap. Second: the scorebook recorded one over against the wrong name. The first, if true, is a rule breach. The second, if true, is an administrative error. Both can be true at once, but neither proves the other.
Bangladesh's own count did not come from the official terminal — it came from their analyst's tally and a Cricinfo scorecard on a phone. That is the least reported and most important detail in the whole affair. A touring team had no direct view of the live official record. It had to trust that the public scorecard reflected it. When the public scorecard is itself built on a faulty entry, the team has no instrument left to catch it.
Distance running offers one useful comparison, and it survives contact with cricket's mechanics. In track, lap counting is never entrusted to one person: bell, lap board, transponder and judge all count separately, and if one disagrees the race is stopped. The logic is simple — when the count decides the result, the count needs more than one witness. Cricket's over count also decides results, and it has one witness. The difference is that a track race can be re-run; a cricket match cannot. Here the remedy runs through the referee's report, not the field.
The dispute is entirely format-anchored. In fifty-over cricket no bowler may exceed ten overs. T20 caps at four. Test cricket has no cap. The incident exists only because this was an ODI. Which means it cannot be imported into T20 or Test arguments — a habit worth resisting, given how readily every umpiring grievance gets inflated into a universal crisis. This is a boundary question, and the question is who was counting at the boundary.
Nor is there a commercial layer. This is a bilateral national-team series: no broadcast stake, no franchise valuation, no auction. Low economic weight means thinner oversight, which is a resource allocation, not a conspiracy. Neutral venues add a distinct channel of risk, because officials are often drawn from a local pool with no standing relationship to the series and no public performance record. That is not bias. It is capacity.
Afghanistan's board has not commented. The match officials have not commented. No formal referee report is public. What exists is one side's account, and its central claim — eleven overs — is an allegation, not an established fact. A board letter reaching the public domain is routinely read as a verdict when it is the opening of a process.

The most interesting turn is that the report buries, inside its own detail, the explanation that weakens the headline. If the scorer-error account is right, Sohail Khan did not bowl eleven overs; the sheet recorded eleven. Different offence, different severity, different remedy. In the first, a captain answers. In the second, the officiating system does.
And the result does not change by itself. Cricket does not retroactively amend outcomes on the basis of a scoring error; a formal protest is possible, rare, and tightly conditioned. Even if an eleventh over was bowled, Bangladesh's defeat is unlikely to be rewritten. That does not diminish the complaint. It defines what the complaint can win: procedure, not punishment.
Which raises the question nobody asked. If one entry in a scorebook is wrong, on what basis are the others trusted? The over count is one column. The same terminal logs runs, wickets, catches, byes, leg byes, no-balls. If a cap handover can move an over to the wrong name, the same crowd can turn a bye into a run. I am not alleging that happened. I am saying the real public cost here is not the over count but the audit trail — and that question was created by the system, not by Bangladesh.
The one piece of good news went under-reported: the argument happened, and then the series ended with a handshake. Disputes metastasise when boards stop talking to each other. Here there was correspondence, two rounds with the referee, and a handshake on the ground. Bilateral channels worked, and that deserves the same column inches as the accusation.
A girl in Tampere reminded me why distant matches matter. Nothing about that afternoon was a broadcast event, and neither is a U19 series in Muscat. Yet this is where the machinery that senior cricket will inherit in a decade gets built — the capacity of officials, the habits of scorers, the level of trust between boards. If an over count can slip through at a neutral-venue age-group fixture, that tells you about the system running the fixture, not about the fixture.
Three things to watch. The match referee's formal finding: if it records that an eleventh over was genuinely bowled, an administrative error becomes a rule breach and the third ODI's legitimacy reopens; if it records a scoring error, the matter closes, provided the ACB does not push back. The ACB's response: silence is an answer, but not one that enters the record. And future appointments for U19 neutral-venue fixtures: an independent cross-checker alongside the scorer, or a mandatory third umpire, would mean the complaint did something; the same officials in the same configuration would mean it died in a filing cabinet.
Whether the eleventh over was bowled is a question about one match, and it may never be answered publicly. The larger question is whether anyone present that evening — player, captain, coach, umpire — had the means to prove the count. In a sport whose results are built from a count of deliveries, one witness to the count is the deepest weakness of all.
