An Over Is Missing From the Muscat Scorebook

The scorer's table at that Muscat ground was set in the corner of the pavilion — a plastic chair, a register, a ballpoint pen, and a glass of water with fingerprints clouding the rim. In a 50-over match, the most power sat at that table and the least scrutiny did too. The man sitting there was deciding which ball belonged to whose name. Two umpires stood in the middle, a third official was somewhere behind a stack of papers, and cricket's most sacred document — the scorebook — rested in one pair of hands. That evening, an analyst with the Bangladesh Under-19 side sat in his chair and counted on his fingers. By his arithmetic, Afghanistan captain Sohail Khan had already completed his ten overs. Then Sohail bowled another one. The eleventh. In 50-over cricket, that count sits outside the law for any bowler — ten overs, and not a ball more. The analyst pulled out his phone, opened the Cricinfo scorecard, and found a ten beside Sohail's name. Two records, two different stories, one match, one evening. In June 2026 at Tunbridge Wells I learned what cricket's real archive is. The BBC was on strike, no camera was present, and Kapil Dev's 175 not out survived only in the memory of the few hundred people sitting there. I filed four hundred words that evening, my editor cut them to ninety, and the rest sat in a shoebox for thirty years. That day taught me that what nobody sees still has to be written down somewhere — otherwise it never happened at all. Muscat is the inverse of that lesson. What happened there was seen, and still was not written down properly. The shape of the story is simple and its layers are tangled. Bangladesh Under-19 and Afghanistan Under-19 played a 50-over series in Muscat — neutral ground for both, home advantage for neither, no familiar bounce off the grass, no crowd pressing down on the boundary. The series finished 2-2. That number is the background music of the whole dispute, because the match under scrutiny was the third ODI, Bangladesh lost it, and in a series pulled level at 2-2 no match is a dead rubber. Every over carries more weight, and so does the losing. After the fourth match, the two coaching staffs came face to face. The argument was over LBW and caught-behind decisions — the kind you can like or dislike but cannot prove wrong. Then the argument stopped, and men from both sides shook hands and talked. That is the moment cricket's temperature falls, and nobody notices it falling. Then the process began, and process in cricket is never quick. The captain's report logged the complaint. There were two rounds of discussion with match referee Yasir Latifzai — two, because the first round usually only gathers grievances and the second decides how serious they are. After that, the Bangladesh Cricket Board wrote a formal letter to the Afghanistan Cricket Board. The letter said, in effect, that Afghanistan's team should be more careful in future. That sentence deserves a second read. Be more careful — the politest and emptiest sentence one board can send another. It contains an accusation without evidence. It offers advice rather than a demand. It does not ask for the result to be changed, or for a specific inquiry by the match referee. And most tellingly, there is no public response on record from the Afghanistan Cricket Board. The story we are reading is one-sided, and in sports journalism a one-sided story is called an allegation, not a fact. Now the rule that fathered the whole quarrel. In 50-over cricket no bowler may deliver more than ten overs — twenty per cent of the fifty, and not one ball beyond. This is not custom or convention; it is a playing condition. Which is why the dispute is ODI-specific. In T20 the cap is four overs. In Test cricket there is no cap at all — a bowler can send down an entire day and nobody asks him to count. Anyone claiming the Muscat episode teaches T20 or Test cricket a lesson is reaching. The controversy was born in the only format where the rule exists. A distinction matters here, because the entire argument rests on it. An LBW decision is opinion — the umpire thought the ball would hit the stumps, you thought otherwise, and opinions do not defeat each other. An eleventh over is not opinion; it is arithmetic. Ten becoming eleven is not a debate, only a count. That is why this complaint does not belong in the drawer where teams file their daily umpiring grievances. It belongs in the drawer marked rule breach. In my years of watching matches, three records always run alongside each other and none of them talks to the others. First, the team's own count, kept in an analyst's notebook. Second, the public scorecard, visible on any phone. Third, the official scorer's terminal, present at the ground and usually out of reach of the visiting side. In Muscat, all three disagreed. Bangladesh's analyst said eleven. The Cricinfo scorecard on the phone said ten. The official scorer recorded ten, and attached an explanation — that one over had been credited by mistake to a player who never bowled it. That explanation matters, because it turns the story. Picture the table. A bowler finishes his spell, hands his cap to the umpire or the captain, the next bowler comes on, the cap goes back, names are called, and in that small scuffle one over lands in a column it never belonged in. This is not the scene of a conspiracy. It is the scene of a man who has been sitting since morning, whose eyes are tiring, with a fifty-over sheet spread in front of him. Cricket's deepest irony is that its most trusted document is made by a human being, and we treat that document as scripture. We do not question the scorebook because the scorebook is where we go to question everything else. If the scorebook is wrong, the place we go to ask questions is wrong. And here the second layer opens — transparency. Bangladesh's team had no access to the official scorer's feed. They were reading a public scorecard, the same one you and I read. So the side that needed to complain held a secondary record of the match. That cuts both ways. On one hand, their eleven-over claim is not as strong as the official record. On the other, if a team playing an international series cannot reach the official record of its own match, that is a governance failure in itself. You are playing on the field and relying on a phone to tell you what is happening in front of you. Sohail Khan's role sits at the centre of this and needs to be understood properly. He captains Afghanistan Under-19 and is simultaneously the side's main bowler. That combination is pressure by construction — leadership and workload on one body. When a boy of eighteen or nineteen has finished his full quota, the decision to hand him the ball one more time is not made in a room. It is made in the middle, by a captain who is both the person deciding and the person executing. None of which means he broke the rule. It means that if someone did, intent is almost impossible to examine. One over is six deliveries. Six deliveries, four to six minutes, and in that time a match can change status — from record to allegation, from player to accused. One figure is enough here, and it has to be translated into a human consequence. Eleven against ten. In a table it is one cell. Behind that cell sits a team that came away level at 2-2 believing it had lost to something outside its control. Bangladesh's real complaint is not the result of the third ODI. It is the belief that the record of a match should be built from the same rules that govern the field. Watching this from Sydney offers a structural advantage rather than a technical one. Pictures reach me a beat late and the scorecard arrives instantly. I read what was written before I see what happened. From outside, it becomes obvious that in cricket the written record is often the actual broadcast. There was no big camera in Muscat, no DRS, no large crowd. The only witness to what happened was that register. When the witness itself is wrong, no second version of the event survives. This sharpens on neutral ground. When a series is nobody's home, the whole hosting scaffold thins out — local ground, local staff, often less experienced match officials. That is not an accusation against anyone; it is the truth of the structure. At Under-19 level, over-management discipline and third-umpire oversight are both thinner than at senior international level. Where oversight is thin, a counting error is the last thing to be caught, because nobody has been appointed to catch it. Which raises the question that will decide the future of this story. If the match referee issues a formal finding that an eleventh over was genuinely bowled in the third ODI, what follows? The honest answer is that cricket does not amend results after the fact. No administrative error changes a scoreline by itself. A formal protest must be lodged, proven, and even then the room to overturn a result is tiny. So even if Bangladesh is proved right, the third ODI will not carry its name. This is where the game's justice system and the game's spirit look at each other and fall silent. Here is what collective memory will not say. When people remember this episode they will file it one of two ways — either Afghanistan broke the rule, or Bangladesh is crying after a loss. Both versions are wrong, and both come from the same mistake: we know events by their drama, not their procedure. The man at that table will not be named in this story. The moment the cap changed hands will never appear in a reel. Yet that moment is the root of the entire dispute. And seen properly, the real news is not that one team accused another. It is that three records of the same match said three different things, and nobody was responsible for reconciling them. I think of that shoebox notebook. I wrote down everything the broadcast missed — cut grass, a fielder muttering to himself, the sound of a bat handle. That was the method: file the seen separately, file the unseen separately, and always write the unseen one first. Muscat ran it backwards. What was seen was not recorded properly, and what was not recorded left no way to be proved. One more thing, the least written and the most important. After the argument, men from both sides shook hands and talked. No boycott, no walk-off, no press release. Two cricket boards with a formal letter between them are still speaking to each other the way they did before. That is good news, and good news never makes a headline. It also means the matter is unlikely to reach the ICC's threshold. This is a bilateral administrative complaint, not a code-of-conduct breach. And until a formal charge is framed, the allegation against Sohail Khan remains exactly that. So the question is not whether an eleventh over was bowled. The question is who audits the register. For four decades we have demanded cameras, snickometers, DRS and slow-motion replays to settle cricket's disputes — while the most basic thing in the game, the counting of overs, still rests on one chair, one pen and one glass of water. That register will be lying closed in a corner of Muscat. One of its pages has ten overs written on it, and that page may never be opened again. The next time you look at a scorecard, hold for a moment and wonder which evening the man behind it is remembering.