When the Scoreboard Falls Silent: Bangladesh Cricket's Lost Overs and Invisible Selections

On the evening of August 20, 2026, I sat in the Rajshahi press box refreshing a schedule on my phone. Dhaka, Sylhet, October 3 to October 20 — the full fixture list for the 2026 Women's T20 World Cup. I refreshed again. The schedule was gone. The ICC announced that day that the tournament would move from Bangladesh to the United Arab Emirates. Two months later, on October 20, New Zealand beat South Africa by 32 runs in the Dubai final to win their first title. Bangladesh survived on the schedule only as a line in a footnote.

That night I wrote in my notebook: when a tournament leaves, it leaves behind an empty scorecard. And an empty scorecard speaks, if anyone is willing to listen.

I first heard that speech in Dortmund in May 2026. I walked into the empty cathedral and heard the silence wearing yellow. Signal Iduna Park held 81,365 vacant seats; Dortmund beat Schalke 4-0, with Haaland scoring in the 29th minute, Guerreiro in the 45th and 63rd, Hazard in the 48th. The echo after each goal was the most honest sound of the day. What a stadium withholds matters more than what it roars.

That silence is not new to Bangladesh cricket. A particular kind has sat here for twenty-five years — the silence of unrecorded overs. Overs that were bowled but never entered into any system. Innings that people watched but nobody logged.

In April 2026, Bangladesh beat Kenya in the final of the ICC Trophy in Kuala Lumpur and qualified for the 2026 World Cup. The scorecard survives somewhere. But what the ball did — which delivery skidded, which bowler was running on empty — has no digital record at all.

On June 26, 2026, at an ICC meeting in London, Bangladesh was granted full Test status. In November of that year, at the Bangabandhu National Stadium, Bangladesh played its first Test against India and lost by nine wickets. The scorecard is public. What the pitch did on day three, whether the ball reverse-swung after tea, is written nowhere.

Here is the first crack. Bangladesh cricket does not lack information; it lacks preservation. When a nation loses the ball-by-ball language of its biggest matches, it also loses the yardstick for its own progress.

In September 2026, at the SSC in Colombo, Mohammad Ashraful scored 114 aged 17 years and 61 days — then the youngest Test centurion in history. Because it was an international match, the record survived, entered a database, stayed in the conversation. In the same year, if a teenager scored 800 runs in the Dhaka Premier League, no trace of it exists. International matches are our national memory; domestic matches are our national inventory. The first is preserved. The second is ignored.

Scorers in the Dhaka Premier League still keep handwritten sheets at many matches. No video, no ball-tracking. At domestic first-class games I have watched a scorer sit with a neat ledger, and at the end of play nobody can say with certainty where that ledger goes. It ends in a club office filing cabinet, or in a scrap paper shop beside a tea stall.

The Bangladesh Premier League, from 2026, produced the first sustained ball-by-ball data in the country. But that data belongs to franchises, not the board; its purpose is broadcast and entertainment, not national selection. The information gathered most is the information used least.

In January 2026, Bangladesh beat Zimbabwe by 226 runs in Chittagong for its first Test victory. Nafees Iqbal made 121; Enamul Haque Jr's spin turned the match. Many of that team came out of a domestic system with no statistical archive at all — club cricket in Dhaka where nothing beyond a single innings score was ever written down.

March 11, 2026, in Chittagong, offers the reverse case. Chasing 226 against England at the World Cup, Bangladesh were 169 for 8. The unbeaten stand between Shafiul Islam and Mahmudullah carried them home. The mental pressure of that passage appears on no scorecard, but it is measurable — dot-ball ratio, required rate, strike rotation against each bowler. We do not measure it, because we do not hold that layer of data.

At the 2026 World Cup in Adelaide, Mahmudullah's 103 against England was Bangladesh's first World Cup century, and the team won by 15 runs. We know the innings as a story. Which over he shifted gears, which bowler he attacked, never reached the analysis, because that data never reached the deadline.

In August 2026 at Mirpur, Bangladesh beat Australia by 20 runs. Shakib Al Hasan made 84 in the first innings and took ten wickets in the match. The data exists here. Yet we usually tell the story rather than the numbers. The matches that give us the most pride are the ones we read least closely, because the story covers the numbers.

At the 2026 World Cup, Shakib made 606 runs and took 11 wickets — the first player to pass 600 runs and 10 wickets in a single World Cup. At Taunton, chasing West Indies' 321, Bangladesh won by seven wickets with Shakib unbeaten on 124 and Liton Das making 94. The team finished eighth. Collective failure buried an extraordinary individual chapter, and the technical explanation of those 606 runs has barely entered our cricket conversation since.

In the 2026 Asia Cup final in Dubai, Liton Das made 121, Bangladesh posted 222, and India won by three wickets. Eight years on we talk about the 121. Which phase he slowed in, which over he attacked, we cannot say.

The second crack sits here. Bangladesh's selection debates rest largely on small international samples, while the large domestic sample sits nowhere. A batter's future is settled on twelve innings while four seasons of Premier League output never reaches a selector's desk.

This is where I have to say the unpopular thing. We treat documentation as heritage work — old scorecards preserved, anniversary editions printed, archives arranged. Documentation is selection infrastructure; it is not heritage, it is a talent-identification instrument. A board without ball-by-ball domestic records must find players by eye, and the eye carries club politics, familiar faces, and yesterday's headlines.

Last year I saw exactly this failure inside a data pipeline. An analysis of a cricket article was run and returned a completely empty payload — no title, no source, no information points, no named entity. The pipeline handed back null silently, with no error flag. The void that does not announce itself as an error is the most dangerous kind. Bangladesh cricket's archive holds thousands of matches of exactly that silent null.

Who pays for the void? The player who stays unrecorded. Suppose a young quick takes seventeen wickets in five matches on an A-team tour in 2026. No video, no ball-by-ball log, a few newspaper reports. Two years later, on what basis does a selection committee pick him? And if he breaks down, who kept the workload count? Bangladesh's fast-bowling injury history is memory-based, not data-based.

Journalists are carrying this load institutionally. In the Rajshahi press box I have watched a colleague dig through an old ledger for a player's domestic record from six years earlier, because it exists nowhere else. Our reporters have quietly become the archive, which is the board's job.

The gap is deeper in women's cricket. In April 2026 in Sylhet, Bangladesh's women beat India in a T20I for the first time. The significance is enormous, but structural domestic data is so thin that a comparative assessment of roles within Nigar Sultana's side is nearly impossible.

Women's cricket carries the largest data deficit, and its scouting depends most on the naked eye — which means the highest bias risk. A player who rarely reaches the media does not get a second look, while an equivalent men's performance is discussed for a week.

Here my own old habit argues with me. At the 2026 BPL final at the Bangabandhu National Stadium, Abahani beat Sheikh Russel 2-0, Chizoba scoring in the 78th and 90+2nd minutes. I sat behind the goal filing only sensation into my phone — the goalkeeper's gloves, the crowd's held breath, the net's shiver. At Bangabandhu, my phone became a notebook and the crowd became a haibun. I filed no statistics that night.

That man now argues the opposite. Kazan in 2026 made the reason plain. In the France-Argentina match I watched Mbappé begin his 64th-minute run from the stands — 60 metres, 11 seconds. In Kazan, the 64th minute opened a trapdoor and the whole match fell through. I learned in Kazan that a time-lapse is just a heartbeat refusing to slow. But who measured the speed of that run? Data. Not feeling.

At Wembley in July 2026, I watched Bukayo Saka's penalty miss in the Euro final and then the silence of 67,000 people from behind the goal. That silence is information. Which minute Italy took control of midfield is not — that requires data. Only the two together make the full picture.

Bangladesh cricket has never painted that full picture. Domestic video archives, ball-by-ball logs, physio and injury records, seasonal pitch notes: with those in place, three things change. The selector's question changes. Fast-bowling workload management changes. And the quality of the journalism changes, because numbers will stand beside the story.

The question is not statistical. It is this: do we actually want to remember our own cricket, or only the matches that were televised? The next time a teenager takes seven wickets in a domestic match in Chittagong, his name should enter a file and not just a one-day headline. Is that really so difficult to guarantee?