The Unwritten Scorebook of Khulna: Is Bangladesh's Spin Supremacy a Story of Pitches, or a Sampling Error?

The western gallery of the Khulna Divisional Stadium is nearly empty. It is the final session of the second day of a National Cricket League match between Khulna and Rangpur in the 2026-24 season. A young left-arm spinner from Khulna has bowled 27 overs on the trot — seven maidens, two wickets. Apart from two or three people sitting nearby, nobody has come to count his balls. The next morning, no national daily prints the scorecard. There is no ball-by-ball log in any online database, only a box score that nobody has verified. And yet the decisions about which spinners enter Bangladesh's Test squad rest precisely on matches like this one. That day I understood something: the match with no footage is the most honest data in this country's cricket — because nobody there is performing for a camera, they are only bowling. For the past decade, the story of Bangladesh's home Tests has hardened into something close to scripture: the slow, turning wickets of Mirpur and Chattogram, plus a trinity of spinners — that formula is supposed to be what makes Bangladesh dangerous at home. Beating England in 2026, beating Australia at Mirpur in March 2026 — those results cemented the story. It is a beautiful story, and beautiful stories always deserve suspicion. I have been coding data by hand since 2026. After joining a Dhaka sports startup as its first data hire, I coded all 44 matches of the BSL football season — 14,200 events. That work taught me that a gap always opens between the evidence and its recognition. Abahani Limited Dhaka had scored 23 goals from 15.8 xG across their first 12 games; my piece was spiked with the line "tactics talk is for the boys." In their next eight matches Abahani scored nine goals and dropped eleven points. The lesson stayed with me: the pattern arrives first, the recognition arrives later. Then I returned to cricket and changed how I work. National Cricket League matches at Khulna, Rajshahi, Bogra and the Dhaka leagues — where scorecards often go unentered and footage does not exist. My job is closer to archaeology than journalism: log every over by hand, then ask what these numbers are actually measuring. I keep the method simple enough that anyone can reproduce it. First I write the hypothesis, then I write the expected result, then I run the query. This rule saves me from two traps — one, the contrarian reflex, where every conclusion must invert the majority; two, false precision, where a clean decimal feels safer than an honest range. So I set today's question down in advance: is Bangladesh's home spin dominance a fact about pitches, or an error of sampling? My expectation: the pitch helps, but a large share of the effect comes from personnel concentration and venue sampling. One thing the reader should keep in mind — I am not campaigning for any decision here. I have a single aim: to show that much of what we call "public" data is actually missing, and that the missingness is itself information. In the narration of Bangladeshi cricket, this is the least discussed truth. A dataset of only a few grounds Bangladesh plays home Tests mainly at the Sher-e-Bangla National Cricket Stadium in Mirpur, the Zahur Ahmed Chowdhury Stadium in Chattogram, the Sylhet International Cricket Stadium, and occasionally the Sheikh Abu Naser Stadium in Khulna. The entire foundation of home advantage therefore rests on a handful of venues. Statistics has a rule: the smaller the sample, the faster a pattern forms — and the faster it breaks. Four grounds mean four different curators, four different bounce profiles, but a single conclusion: "Bangladesh is spin-dependent at home." That conclusion erases the diversity of the venues themselves. While coding Khulna's matches by hand, I noticed something. The Khulna wicket is not like Mirpur's — the new ball seams more here, and spin arrives slowly, after the second day. In other words, this country's home pitches are not one thing at all; the variation is large. But in the national narrative they collapse into a single image. There is a further dimension — curation. The same stadium produces a different wicket from season to season, because different people prepare the pitch under different instructions. So "the Mirpur wicket" is not a permanent entity at all. Yet our language makes it permanent, and that is exactly when venue-based decisions go wrong. Count the overs, not the wickets The real number hides here. Over the past decade, a huge share of all overs bowled in Bangladesh's home Tests was delivered by just three men — Shakib Al Hasan, Taijul Islam and Mehidy Hasan Miraz. I have tried to extract the over-share from my own logs, and every time I find the same picture: the lead spinners take the lion's share of the overs, and the rest mostly keep an end warm. The career overlap of those three created a specific window — 2026 to 2026. In that period all three were fit almost simultaneously, and Bangladesh's home record was at its best in exactly that window. The question: is that coincidence, or evidence of personnel dependence? I lean toward the second, while accepting the limits of the evidence. This is where the question turns. If we call spin dominance a "system," the expectation would be that when one spinner drops out, another takes the same role, the same economy, the same share of overs. I wrote the hypothesis down in advance: with one of the three absent, the replacement's over-share would rise and the economy would stay within ±0.3. The actual result differed — the economy rises more, and the strike rate worsens too. So what we think of as a system is really a cluster of individuals. The numbers were not lying; they were waiting for a better question. A small sample inside the sample There is another layer almost nobody opens. A large share of Bangladesh's home Test wins came against specific opponents — Zimbabwe, a weakened West Indies, Afghanistan. Against stronger sides, home success is far rarer. So the "home advantage" number is mixing two different things: the quality of the opposition and the benefit of conditions. Without separating them, we credit the conditions for success that is really an artefact of the schedule. I tried to split the two in my own log, and the result is uncomfortable: against stronger opponents at home, the over-share pattern stays almost the same, but the economy rises. The system holds, but the system is not enough. This is the place where the phrase "spin supremacy" feels a little too comfortable. The unwritten archive of Khulna To find the cause of this personnel dependence, you have to go to unrecorded places. The National Cricket League has eight teams — Dhaka, Dhaka Metropolis, Chattogram, Khulna, Rajshahi, Barishal, Rangpur, Sylhet. Many matches in this league have no broadcast and no ball-by-ball log. So the question becomes: if the replacement pool is built anywhere, it is built here, but we cannot measure it. A dataset that is not measured is not managed either. Khulna Division's record is instructive. Shakib Al Hasan was born in Magura, Mustafizur Rahman in Satkhira — both in Khulna Division. The region has produced talent, but there is no disciplined record of how that talent was made, at what workload, with what bowling spell. We get the output; the process disappears. In Khulna I learned that silence is also a dataset. The overs that never entered anyone's log are the ones that tell you who is carrying how much load. The bodies of young pacers Behind the home spin story, one number is always buried — pace workload. In the NCL, the over-load on young pacers is often uncontrolled. At a home match in Khulna I watched a 20-year-old pacer bowl 21 overs in the first innings and 17 more in the second. Thirty-eight overs in two days — at the very age when shoulder and back load management matters most, the boy is bowling like a senior. The process is inverted: the one who is not yet physically finished is being given the heaviest load. My position is clear, but it is not a slogan — I simply choose the cases. Overusing young pacers means we are taking profit now at the price of future damage. Bangladesh's real peak curve (where a pacer tops out between 26 and 30) is not the peak curve imported from SENA conditions. We routinely judge the first by the second — and that is the measurement artefact. The illusion of the heatmap There is another layer. Modern coverage presents heatmaps and wagon wheels as if they were proof. But trying to read a spinner's role from his heatmap is close to reading tea leaves. A heatmap shows where the ball went; it does not show why it went there. That left-arm spinner in Khulna bowled the same line and length for his first 15 overs because the captain had him in a "holding" role — so that the attack could come from the other end. On a heatmap that looks monotonous; inside the team system it was the most valuable work on the field. Lose the role and the number deceives you. The bowler who was never picked My most valuable findings are usually about the things that did not happen. Between 2026 and 2026 there were spinners in the NCL whose home economy was better than that of the main squad's spinners, but who were never called into a Test squad. Why? Because the selection process measures the "spike," not the "pattern." A five-wicket innings catches the eye; six months of 2.2 economy does not, if it is not logged anywhere. The spike got spiked, but the pattern stayed in the data. One verifiable fact: Mustafizur Rahman was born in 2026 in Satkhira (Khulna Division) and made his ODI debut against India in June 2026 — per the BCB and Cricinfo player profiles. But the ball-by-ball data of his NCL over-load before that debut is stored nowhere. We have preserved the output, not the process. The cost nobody accounts for There is a cricket version of football's loan-with-obligation model, and nobody writes it down. NCL sides — especially smaller setups like Khulna, Rajshahi and Barishal — spend years developing a young player. Then a BPL franchise or the national team takes him, and the base layer gets back only a name. The system that carries the cost is excluded from the decision. The result: there is no incentive to keep records at the base, because even if you keep them, the share of the profit never returns. An institution that does not measure its own loss does not recognise its own assets either. The limits of my method Honesty is required here. My NCL log is not complete. I have watched the Khulna and Rajshahi home matches in person, but I do not hold the records of many Sylhet or Barishal matches. So the picture of over-share I am drawing is partial — it indicates a direction, it is not conclusive proof. Rather than a clean decimal, I want to give a range: my estimate is that 50 to 70 percent of the spin-dominance effect in home Tests can be explained by personnel concentration and venue sampling; the rest is pitch and conditions. Without stating that limit, the number becomes armour rather than evidence. Here I want to avoid my own trap. Being "contrarian" is not my profession, it is my method. So I will say it honestly: spin works at home — that is true, and the pitch plays a big part. The question is not about the pitch. The question is whether we have mistaken a cluster of individuals for a system. The likely answer: yes, partly. Because it is not only the relationship between pitch and spin — wins come from the weakness of the opposition, the toss, the weather, and three spinners being fit at the same time. Unless those factors are separated, correlation is mistaken for cause. And that is precisely when a future "sudden collapse" fails to be sudden — it was visible in the data for years, nobody just logged it. The real blind spot is not the pitch, it is the pipeline. We measure the top layer and ignore the base layer. A system that keeps records only at the summit feels the loss of its foundation all at once. Next season I will not look at the wickets column. I will look at who bowls the 40th over of the day, and at the NCL scorecards nobody has entered. My model is a prayer — until the data says otherwise. And a large part of that data is still lying in some unwritten scorebook in Khulna, on rain-soaked pages. The question is now yours: will you preserve only the results, or the process too?