The Scorecard That Was Never Written: Khulna's Unwatched Matches Are Bangladeshi Cricket's Real Dataset

In a club-level match in Khulna, I found a scorecard that recorded a bowler taking 4 wickets for 12 runs in 10 overs. The problem was simple: there was no record of the other 40 overs. No ball-by-ball log, no footage of field placements, no complete list of batters' names. Just some numbers on a piece of paper that no one had ever verified. My first reaction: is this 4-wicket haul a real performance, or a measurement artifact—where we only see the part someone remembered to write down?

Over the past 19 years, I have trawled through scorecards from Mirpur's press box to Khulna's club grounds. A pattern keeps returning: conversations about Bangladeshi cricket almost always rest on a specific dataset—primarily international matches, televised domestic leagues, and a few big names' career graphs. This dataset is convenient because it is easy to record and verify. But it is incomplete. Because the most cricket in Bangladesh is played on grounds without cameras, where the scorer writes in a personal notebook, and that notebook disappears after the match.

In 2026, I hand-collected the scorecards of 27 matches from a Khulna Division club tournament. Of the 3,240 balls bowled, ball-by-ball detail existed for only 1,900. The remaining 1,340 balls had no detail—only the aggregate score. That gap is my core finding: what we analyze as 'Bangladeshi batter's consistency' or 'bowler's workload' is largely built on the 59 percent of data that was recorded. The other 41 percent—where there was probably the most struggle, the most experimentation, and the most error—sits in complete darkness.

Is this darkness just administrative neglect? No. It is a systematic bias. Suppose a 19-year-old bowler sends down 28 overs in a three-day match in Khulna. The scorecard reads '28-5-67-3.' But how many of those overs did he bowl while exhausted? How many overs did his line and length break down? Against which batter was he forced to bowl with an attacking field? Without this information, we cannot build his workload model. Yet national selectors make decisions precisely on scorecards like these—deciding who is ready and who is not.

A counter-argument arises here: domestic cricket is of such low quality that the analytical value of this data is limited. My answer—when quality is low, the need for data increases, not decreases. Because low quality means high variance, and high variance means we need more samples. In an international match, a bowler's economy rate of 4.2 is significant because the opposition's quality is high. But in a domestic match, the same bowler's 4.2 economy carries much less information because the average quality of the batters is unknown. To fill that unknown, we need ball-by-ball data from those matches—which no one collects.

When I joined a Dhaka digital sports startup in 2026 as its first data analyst, my first task was to hand-code 14,200 events from 44 Bangladesh Premier League matches. That experience taught me that collecting data is itself reporting. If you only look at results, you see the summary of history. But if you look ball-by-ball, you see the construction of history. Those 1,340 unrecorded balls in Khulna are exactly part of that construction that stays outside our vision.

Let me give a specific example. In a 2026 National Cricket League match, a young Khulna Division pacer bowled 14 overs in the first innings. The scorecard showed 3 wickets next to his name. But in the second innings, he was given only 6 overs. Why? No footage, no report. Perhaps he was tired, perhaps he was injured, perhaps the captain did not trust him. Each of these possibilities has a different meaning for future selection. But we have only two numbers: 14 and 6. These two numbers do not tell a story. The numbers were not lying; they were waiting for a better question.

One principle of my work: what is not seen is also data. In Khulna, I learned that silence is also a dataset. The ball with no video may have been the most important ball of the match. The innings cut short by rain may have been on its way to a century. We do not count that century because it was not completed. But in analyzing player development, incomplete events are equally important. If a match is washed out, the workload of a bowler who played is not zero—he may have bowled 5 overs before stopping, and his body bore the stress of those 5 overs. But in our models, those 5 overs are nowhere.

Now to the center of this discussion. In current conversations about Bangladeshi cricket, the phrase 'golden generation' is very popular. The success of this generation rests largely on international match data. But when I place domestic scorecards side by side, a different picture emerges. A player who averages 30 in the national team averages 45 in domestic matches. That is no surprise. But the real question is—why the difference? If the difference is only in opposition quality, there is no problem. But if the difference is in style of play—say he is more comfortable against spinners in domestic matches but struggles against pace in international matches—then that is a tactical crisis. And we do not get evidence of this tactical crisis because there is no ball-by-ball data from domestic matches.

Another issue matters. Age verification is a major challenge in Bangladesh. I have seen many players in under-17 sides whose physical build looks like 21. One major reason for this discrepancy is that we lack reliable age-verification data. But there is another reason, less discussed: we impose pressure on young players too quickly because our observation system is weak. When a bowler takes 4 wickets in an unrecorded match, he immediately becomes a 'find,' without any analysis of how many overs he bowled, what his recovery time was, or whether his action breaks down under fatigue. This rapid pressure breaks many young talents before they even reach the international stage.

A counter-argument is needed here. Some might say domestic cricket is of such low quality that analyzing data from it easily leads to wrong conclusions. That is true. Sample limitations are a reality. The data from the 27 matches I collected does not in any way represent all of Bangladeshi domestic cricket. It is a small, non-random sample. But here I want to make my position clear: I am not claiming that final truth can be extracted from this data. Rather, I am saying—such data can be collected, and it should be collected. Because until we map this dark zone, our analysis will largely rest on assumption.

Every model is a prayer until the data says otherwise. Those 1,340 unrecorded balls in Khulna are like that prayer to me—with no answer. But having no answer is also an answer. It tells us there is a structural gap in our observation system. Until that gap is filled, we will never know where Bangladeshi cricket's real talent is hidden. Not under Mirpur's floodlights, but on Khulna's club grounds, where no one brings a camera.

At the end of this discussion, one question remains. The Bangladesh Cricket Board appointed advisors on digital and media affairs in 2026. That initiative has an opportunity—to institutionalize data collection from domestic matches. But the question is, will they only digitize Mirpur's scorecards, or will they also take cameras to Khulna's unseen matches? If the answer is the second, Bangladeshi cricket analysis will stand on a new foundation. And if it is the first, we will continue living with that 41 percent darkness—and believing we are seeing the whole picture.