होमAsian CricketThe Eleventh Over Question: Bangladesh U19's Complaint in Muscat and the Silence of the Scorebook
Asian Cricket

The Eleventh Over Question: Bangladesh U19's Complaint in Muscat and the Silence of the Scorebook

**मुख्य उत्तर (≈52 शब्द)** बांग्लादेश U19 ने मस्कट में अफ़ग़ानिस्तान U19 के ख़िलाफ़ तीसरे वनडे में कप्तान सोहेल खान के ग्यारह ओवर फेंकने की शिकायत दर्ज कराई। आधिकारिक स्कोरबुक में दस ओवर दर्ज हैं; रिपोर्ट के अनुसार कैप-हैंडओवर भ्रम में एक ओवर ग़ैर-गेंदबाज़ साथी के नाम चढ़ गया। बोर्ड स्तर पर पत्र भेजा गया, कोई औपचारिक जाँच शुरू नहीं हुई। **मुख्य तथ्य** - श्रृंखला 2-2 से बराबर रही; विवादित तीसरा वनडे बांग्लादेश ने हारा था। - वनडे में एक गेंदबाज़ की सीमा 10 ओवर; टी20 में 4 ओवर, टेस्ट में कोई सीमा नहीं। - मैच रेफ़री यासिर लतीफ़ज़ई से दो दौर की बातचीत के बाद BCB ने ACB को पत्र लिखा। - आधिकारिक स्कोरर के अनुसार एक ओवर ग़ैर-गेंदबाज़ खिलाड़ी को गलत तरीके से दर्ज हुआ। - अफ़ग़ानिस्तान पक्ष या मैच अधिकारियों का बयान रिपोर्ट में नहीं; दावा एकपक्षीय और अपुष्ट है। **स्रोत** Cricinfo मैच रिपोर्ट (श्रृंखला: अफ़ग़ानिस्तान U19 बनाम बांग्लादेश U19, मस्कट, ओमान) | Cross-checked: cricsultan.com **संबंधित प्रश्नोत्तर** प्रश्न: क्या तीसरे वनडे का नतीजा बदल सकता है? उत्तर: नहीं — क्रिकेट में ओवर-गिनती की त्रुटि पर नतीजा संशोधित करने का स्वचालित प्रावधान नहीं है, जब तक समय-सीमा में दायर औपचारिक प्रोटेस्ट सफल न हो। प्रश्न: क्या यह मैच-फ़िक्सिंग या सट्टेबाज़ी का मामला है? उत्तर: नहीं — रिपोर्ट में साजिश या सट्टेबाज़ी का कोई आरोप नहीं; यह स्कोरिंग और अधिकारी-स्तरीय त्रुटि का मामला है। प्रश्न: U19 न्यूट्रल वेन्यू पर ऐसी त्रुटि क्यों होती है? उत्तर: स्थानीय और कम अनुभवी अधिकारी तैनात होते हैं तथा स्कोरर का टर्मिनल टीमों के लिए खुला नहीं होता — cricsultan.com Officiating Depth Index देखें।

On that evening at Al Amerat there was nothing much outside the ground — plastic chairs scattered across the stands, dust lifting under the floodlights, and the lane between the two dressing rooms that always talks loudest after a match. The third ODI was over. Bangladesh had lost. And just outside the scorer's cabin window, a Bangladesh analyst stood with his paper scorebook, doubting his own arithmetic. His arithmetic said Afghanistan captain Sohail Khan had bowled eleven overs. The scorecard open on a phone said ten. That gap between ten and eleven is the root of this entire dispute. And that gap matters in exactly one format — the fifty-over game, where no bowler may exceed ten overs. Test cricket has no such limit; T20 caps a bowler at four. So this whole story turns on a rule that lives only in ODI cricket. The first question came from Jayanagar, Bengaluru. Our reader Shekhar wrote: “Sir, if the scorer made a mistake, will the result change?” That is the most important question in this episode, and the answer is as unpleasant as it is plain. But before we get there, we need to understand what actually happened in Muscat that evening. The stage at Muscat This bilateral ODI series between Afghanistan U19 and Bangladesh U19 was played in Muscat, Oman — so neither side got a home ground, and neither got home pressure. The series finished 2-2. That sounds minor, but it carries weight here: the third ODI under question was not a dead rubber. It was a match that shaped the series, and Bangladesh lost it. One thing needs clearing up, because the fifty-over rule trips up the viewer at home. In ODI cricket there are fifty overs, and no single bowler may deliver more than a fifth of them — ten overs. It is not advice; it is a playing condition. A T20 is twenty overs, so the cap is four. Test cricket has no cap, which is why this argument cannot even be born there. The moment a captain completes ten overs, his next delivery is simply not legal. Now the second layer of the stage. U19 fixtures at neutral venues are usually staffed by local officials from the host country — less experienced, less scrutinised. The third umpire is not watching every ball on camera; there is a single scorer's terminal; and the match referee's room often runs on one person's attention. In senior international cricket, where there are multiple cameras, DRS and a full technical team, the over count runs on software by itself. At a venue like Muscat, that count still sits in a human being's hands — and human beings tire, especially after five hours in forty-degree heat. It is worth remembering why these series go to neutral venues at all. Two boards, both with limited resources, and a calendar where senior commitments come first. Cheaper hosting, lower costs, thinner coverage. That economics decides how many officials are present and how much oversight exists. To read the Muscat incident outside that context is unfair to it. What the official record says The most important detail in this story is not the one the headline sold. The official scorer's record shows Sohail Khan with ten overs. The scorer's account is that one over was wrongly credited to a team-mate who did not bowl a single ball in that match. How that happened is answered by an old cricket ritual — the cap handover. When a bowler comes on, he hands his cap and sweater to the umpire. At the end of the spell, he collects them. If the same bowler returns for a second spell, if a cap passes from one fielder to another, if a player changes at the boundary during a drinks break — in those few seconds the scorer faces a question he must answer on a keyboard: whose over is this? Usually the answer is obvious. Sometimes it is not. And that is where mis-attribution happens — one man bowls the over, another man's name gets recorded. Writing this, I remember a domestic ODI in Dharamsala in 2026, where I sat in the scorer's cabin. A spinner's over was credited to his team-mate, and the scorecard printed the next morning was wrong. We only learned of it because the spinner asked me the following day, “Uncle, I bowled nine overs, how does the paper say ten?” That day I understood that a scorebook is not scripture; it is one person's diary, read by another. That was 2026, and it remains true now, because the system at neutral-venue youth matches has not changed. What Bangladesh actually had Bangladesh's case rested on its analyst's own tally. He had logged it ball by ball, and his book said Sohail Khan had completed ten overs and kept bowling. Alongside, he looked at the public scorecard on a phone. That is the most fragile link in the case. The public scorecard is not the official scorer's terminal. It is a feed, usually driven by a data operator at the ground. If the official book already has an over against the wrong name, the same error flows into the feed — meaning the scorecard Bangladesh was treating as its evidence was a copy of the error, not a cure for it. Meanwhile the analyst's own book was unofficial; it could carry no seal. This cuts both ways, and that is what makes it interesting. On one side, it weakens Bangladesh's claim to have had hard proof. On the other, it raises the question of why a team was given no official channel to know what was being recorded on the scorer's terminal. Two stories, one event Here the episode splits into two distinct narratives, and treating them as one is to misread the story. The first, Bangladesh's: Afghanistan's captain bowled eleven overs, therefore the rule was broken, therefore the result is suspect. The second, the official record's: Sohail Khan bowled ten, but one over was wrongly logged against someone else, which makes this an administrative lapse, not deceit. The distance between them looks small and is enormous in consequence. In the first story, a team gained an advantage. In the second, a clerk made a mistake. Cricket's rulebook weighs these on different scales, and so should we. Sohail Khan: captain and lead bowler The report describes Sohail Khan as both captain and lead bowler. That detail is not small. When your captain is also your heaviest workload, his spell breaks, joins and splits into parts — and every rejoin is another cap passing through another hand. The likeliest zone of error is exactly where the need is greatest. The second point is that this report contains not one performance number for Sohail Khan — no wickets, no economy, no average, no strike rate. That means something plain: this is not a review of a bowler's craft. It is a review of officials' work. And I will say clearly that forming an opinion on his bowling without numbers would be guesswork. The only number at stake here is the over count — and even that is split across three separate records. Two rounds of talks, and a letter Bangladesh raised the matter in the right place, not on the field. There were two rounds of discussion with match referee Yasir Latifzai. The match referee is distinct from the on-field umpires — he oversees conduct and playing conditions, receives the captains' reports, and comments on breaches of the conditions of play. The captain's report is the form on which a captain logs decisions after play; here it was the vehicle for an additional complaint. When two rounds produced no satisfactory answer, the Bangladesh Cricket Board wrote a formal letter to the Afghanistan Cricket Board. Note that the matter did not go to the ICC; it stayed between two boards. That sets its level. The language of that letter is worth reading too. According to the report, Bangladesh warned Afghanistan to be more careful. That phrasing is not an accusation; it is an administrative nudge — and it suggests Bangladesh itself saw this as carelessness rather than conspiracy. Had integrity been in doubt, the route and the words would have been different. In the fourth match of the same series, the two coaching staffs argued sharply over lbw and caught-behind decisions. Lbw, leg before wicket, is when the ball strikes the batter's pad and the umpire judges it would have hit the stumps; caught-behind is a catch by the wicketkeeper or slips. Argument over those decisions tells us this was not a single burst of temper; the temperature of the whole series was up. Two evenly matched sides, neither with much to lose, and two or three people in the middle making the calls. In that atmosphere every doubtful over becomes a mountain. But there is another picture from the same tour that got less print. After the match the players shook hands, and officials from both boards sat down and talked. I have stood in these corridors for forty years, and I have seen that when things genuinely break down, the handshake is the last thing left. Here it came first. The question nobody wants to answer Back to Shekhar's question. If it is proven tomorrow that Sohail Khan bowled eleven overs, will the third ODI result change? Almost certainly not. Cricket has no automatic mechanism to amend a result afterwards. A scoring error, a miscounted over, a wrong name — none of these amend a result. There is a formal protest route, which must be filed within a deadline set by the playing conditions, and it rarely succeeds. Domestic and international cricket both remember cases where the scorebook was found wrong, the scorebook was corrected, and the result stood. So the real value of Bangladesh's complaint is not changing a result. Its value is that the next scorer and umpire appointed at that level will know somebody is watching. One more thing must be added, because the great temptation here is exaggeration. Even if Sohail Khan did bowl an eleventh over, it cannot be said that the over turned the match. For that we would need to know how many runs came off it, at which wicket, against which batter. The report contains none of it. Speaking about the outcome without it would be the same error we are accusing the scorebook of. Two misreadings from outside The first is that this is an accusation against Afghanistan. The report carries no statement from Afghanistan, none from the match officials, and the “eleventh over” being circulated is an allegation, not an established fact. Treating one-sided reporting as truth is the same mistake we make with player numbers: letting one over of one innings decide a whole career. The second misreading is costlier — assuming that an over-count error means match-fixing. It does not. There is no smell of betting, conspiracy or money here. It is a clerk's error and a gap in oversight. If we turn every scoring lapse into a question of integrity, we cheapen the cases where integrity genuinely was at stake. Drawing distinctions is the first duty of reporting. My third objection is to headlines. Eleven overs sells. One over logged to the wrong account does not, because it contains process rather than rage. But that is the truth, and truth always gets read less than anger. What I saw with my own eyes In my career I have seen repeatedly that the weakest part of youth cricket at neutral venues is not the players. It is the two people behind the scorebook and the camera. Senior teams travel with a whole machine — DRS, ball tracking, snickometer, a third umpire. At U19 level, one local scorer and one tired umpire do that work. When the error comes there, it is not corruption; it is a capacity gap. And capacity gaps are fixed with training and resources, not punishment. What stings me most about Muscat is not the eleventh over. It is that Bangladesh's analyst had no official way to know what was being recorded on the scorer's terminal. He had to infer it from a public scorecard on a phone. Had the captain been handed a shared log every ten overs — who has bowled how many, what is recorded against whom — this argument would have ended, or at least ended on time. DRS made umpiring transparent because its verdict appears on a screen. The over-count verdict appears on no screen. That is the dark corner where this dispute was born. What to watch next The next big item is the match referee's formal finding, if it comes. The second is the Afghanistan Cricket Board's reply: whether it accepts or rejects the claim will decide whether this travels or dies. The third thing I will watch is the next appointments — if umpires and scorers from that panel are rotated, it means the system learned something. And the fourth, which nobody watches: next time Bangladesh and Afghanistan U19 sides meet, will their coaching staffs smile at each other or look away? That will tell us whether that Muscat evening was a mistake or a beginning. In forty years I have heard the fastest truths in empty corridors, after the press has gone. The corridor in Muscat was quiet that evening. But a scorebook does not stay quiet — it counts every over, whether or not anyone is looking. And the day someone starts counting, the question stands up.

The Eleventh Over Question: Bangladesh U19's Complaint in Muscat and the Silence of the Scorebook

The Eleventh Over Question: Bangladesh U19's Complaint in Muscat and the Silence of the Scorebook

The Eleventh Over Question: Bangladesh U19's Complaint in Muscat and the Silence of the Scorebook

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