The Eleventh Over: Bangladesh's Claim, a Warning to Afghanistan, and One Wrong Line in the Scorecard

Three records were giving three different answers about the overs of one bowler at a ground in Muscat. Bangladesh U19's analyst had counted, and said Sohail Khan's ten overs were done, so the next one was outside the law. Afghanistan's captain was at the top of his mark for that next over. And the official scorer's terminal credited Sohail with ten — because the eleventh had been entered against a team-mate who never bowled it. The dispute begins on that single line: three sources, one number, and none of them corroborating the other two.

Take the format first, because without it the argument is unfinished. This was a four-match bilateral 50-over series in Muscat, a neutral venue for both sides, and it finished 2-2. The third ODI was therefore not a dead rubber — it was the match Bangladesh lost, and the dispute sits squarely on its over-count. The rule at the centre of it is that in 50-over cricket no bowler may deliver more than ten overs, twenty per cent of the innings. T20 caps a bowler at four, Test cricket sets no cap at all. The controversy is therefore ODI-specific and cannot be carried into T20 or Test discourse. Bangladesh Cricket Board raised the matter across two rounds of discussion with match referee Yasir Latifzai, then wrote formally to the Afghanistan Cricket Board, asking Afghanistan to be more careful. After the fourth match the two coaching staffs argued over lbw and caught-behind decisions; the exchange ended with a handshake.

Now the substance, and this is where the coverage goes wrong. Bangladesh's claim is that Sohail Khan bowled eleven overs. The official record says ten, and adds that the eleventh was credited to a team-mate in a cap-handover mix-up. Those are two different claims, and merging them is the commonest error in the reporting. One says a playing condition was broken; the other says a record was written incorrectly. If the first holds, the match's legitimacy is in question. If the second holds, this is a clerical failure that gave birth to the first. When Bangladesh checked their count they did not have the official scorer's feed; they had a Cricinfo scorecard open on a phone and their own analyst's sheet. In 2026 I hand-tagged roughly nine thousand deliveries on the night shift of a Dubai data vendor. What I learned that season is that every clean dataset I trust has a night shift buried somewhere inside it, and here the night shift is the scorer's terminal, which nobody read while the match was live.

The report carries not one performance figure for Sohail Khan — no wickets, no economy, no strike rate, no phase splits. That absence is the most important fact in it, because it tells you the subject here is officiating, not bowling. The only number in play is the over-count itself, and it is contested between three records. Sohail is captain as well as the side's main bowler; that concentration of workload makes an extra over plausible to miss, and it magnifies the consequence if the over was genuinely bowled.

Put the setting in neutral language: a neutral venue, an Under-19 fixture, two developing cricket nations. Officiating capacity — umpire and scorer both — is the weakest link at that tier and the least supervised. No fixing allegation has been raised anywhere; this is an officiating-error matter, and collapsing the two is the same carelessness as printing two decimal places when the interval is several times wider.

Here is the null hypothesis first: is it possible the over-count genuinely went wrong and Bangladesh's complaint is directionally correct? Yes, plainly. The scorer conceded that an over landed in the wrong account — the record did contain an error. That does not mean the result changes. Cricket does not retroactively amend results for clerical errors; a formal protest succeeding is rare and carries no published probability. Second, the report carrying this story quotes neither the Afghanistan board nor the match officials — it is a one-sided document, and eleven overs is an allegation, not an established fact. Third, the detail the headlines drop: the post-match confrontation ended with a handshake. That is data too, and it says escalation risk is lower than the framing implies. One over is an observation; it is not a finding about a bowler's discipline.

What to watch is specific. The match referee's formal finding — whether it records an eleventh over or only a scoring error. The Afghanistan board's response — concession or denial. And the item that matters most: whether scorer and third-umpire protocols change for Under-19 fixtures at neutral venues. I do not forecast outcomes; I forecast the size of my own ignorance — and right now that size is exactly one over wide, with no publicly verified scorecard of it in existence.