Ten Overs in the Book, an Eleventh in the Letter: Which Over Is Actually Missing from the Muscat Scorecard

The official scorecard credits Sohail Khan with ten overs. Bangladesh's analyst had those ten overs ticked off before an eleventh began. The scorer's terminal also shows ten — the only difference is that one of them is logged against a bowler who did not send down a single ball that innings. Three records, one match, and three different answers to whether a particular over exists. The entire dispute from the Bangladesh U19 versus Afghanistan U19 one-day series in Muscat sits on that single over, and the letter the Bangladesh Cricket Board sent to the Afghanistan Cricket Board alleges eleven overs — while the official record of the same event says ten, one of them in the wrong column. Those are not the same claim, and reading them as one means reading the whole story wrong.

The rulebook says ten overs; the field read it in the eleventh — that is the whole case in one line.

Settle the format first, because this controversy is format-specific. This is 50-over cricket, where a bowler is capped at ten overs, twenty per cent of the innings. T20 caps him at four; Test cricket caps him not at all. So if a captain genuinely bowled an eleventh over, that is not a bad umpiring decision, it is a breach of a playing condition. And if the scorecard contains no eleventh over, the issue is not a rule breach at all but record-keeping. The distance between those two readings is the actual subject of the letter.

The shape of the series carries weight too. This was a bilateral U19 series hosted at a neutral venue, Muscat in Oman, so neither side had home advantage. The series finished 2-2, and the contested third ODI was the one Bangladesh lost. That detail matters: the match was not a dead rubber, the result was built on a close margin, and the complainant is the side that lost it. After the fourth ODI the two coaching staffs argued over LBW and caught-behind decisions, then shook hands and talked it through. A tight, emotionally loaded series — exactly the environment in which questions get asked about officials.

Now walk the record backwards. I build timelines from the registered document, never forwards from the whisper. The registered document here is the scorer's sheet, and the sheet has no eleventh over. What it has is one over credited to the wrong account: at a cap handover, according to the scorer, an over was logged against a teammate who never bowled it, and the error was not caught.

Bangladesh's version runs differently. Their analyst counted and found Sohail Khan had already sent down ten; the team checked a Cricinfo scorecard on a phone. That surfaces a fact inconvenient to both sides: Bangladesh had no access to the official scorer's feed; their tracking rested on a secondary source. That weakens their claim and sharpens it at once — weaker because it is not the official record, sharper because if the official record was crediting an over to the wrong bowler, an outsider had no mechanism to correct it.

The formal process is visible. The matter went to match referee Yasir Latifzai across two rounds of discussion, then the BCB wrote to the ACB, warning the Afghan side to be more careful. That is the textbook escalation path: captain's report, match referee, board-to-board correspondence. Note what is absent: no public information shows an ICC formal charge or code-of-conduct action — this is a bilateral administrative complaint, not a disciplinary proceeding.

Keep two sourcing tiers apart. Documented: ten overs on the scorecard, the ODI ten-over cap, the referee's name, the board-level letter, the 2-2 series score. Credible but unstamped: that an eleventh over was actually bowled. The second tier should not be deleted — records trail reality, and the news lives in that gap — but it should not be merged into the first.

Here is the rival frame, and I will let it stand un-refuted for a paragraph: Bangladesh is externalising a defeat onto officials rather than onto its own record. That reading is not absurd. The complainant lost the third ODI; the coaching staffs argued after the fourth; the central piece of evidence is a scorecard viewed on a phone. Sit in the ACB's chair and your first question is how durable an allegation is when it rests on a third-party website rather than the official scorer's terminal.

Accepting that frame does not erase a second, more important one: at a neutral-venue U19 series, officiating capacity is the weakest link, and that is a structural gap rather than a question of anyone's intent. In junior and associate cricket, third-umpire oversight, scorer terminal protocols and cap-handover procedure are thinner than at senior international level. From two decades of watching scoring desks at junior and associate fixtures, one thing is clear: an over-count error there is a routine procedural lapse, not an exotic one. The question is not whether someone can err. It is where the second set of eyes was.

One cold fact should not be buried under sentiment: cricket does not retroactively amend a result for this kind of error. Successful formal protests are vanishingly rare, and in a bilateral U19 series the scope is effectively nil. Even if an eleventh over was bowled, Bangladesh gains no win on the scorecard — what it can gain is a recorded finding that the record was flawed.

The real weight of the case lies in what can and cannot be established. The scorer's procedural lapse can be established, because its mechanism is public. The eleventh over cannot, until the ACB or the referee's office states its side — and in the available material that side does not exist. This is one-sided reporting, and one-sided reporting deserves two thoughts before it is granted the status of fact.

Two scorecards, one match — and the same over missing from both. The next move is on paper, not on grass: whether the match referee's formal report records an over-count error in the third ODI, whether the ACB concedes or contests the allegation, and on what basis scorers and third umpires are appointed for the next neutral-venue U19 series. The odds on the result changing are slim. But the next time a captain completes ten overs and an eleventh begins, the question returns — whose count is it, the scorer's or the screen's.