The Rangpur Ledger: The Balls Asian Cricket Never Counts

The Rangpur Ledger: The Balls Asian Cricket Never Counts

A hunch, then a correction

On an evening last February, a seventeen-year-old left-arm spinner took nine wickets in a district-level match in Rangpur. His name went up on the scoreboard, two lines of the result appeared in a local daily, and then the performance entered no database at all. I did not watch the balls live; nobody filmed them. All I had was a photograph of a handwritten scorebook, handed to me by a veteran scorer who said, "You might need this."

That scorebook is where this piece begins. For years I have cultivated one habit — to keep count of what others do not see. This article chases no star's name, no final's highlights. It is about the numbers that never appear on a television graphic, and yet it is precisely there that Asian cricket's true depth is hidden.

I began with a hunch, then let the ledger correct me. The hunch was simple: Asian cricket does not lack talent, it lacks the apparatus for counting. So far that hunch has proven the most correct of all — because the deeper I went, the more the pile of uncounted performances revealed not a shortage of ability but a shortage of accounting.

Context: how a ledger is born

My name is Ethan Moore. Born in Pakistan, I now work in Bangladesh. In 2026 I left The Daily Star to become a correspondent following the national team — home and away, two cultures, two kinds of cricket bureaucracy. In 2026 I made my own ODI debut, an international career that ran until 2026. The biggest lesson of those days was not batting or bowling — it was that half of cricket's truth is never written on a scorecard.

In 2026, at forty-four, I launched the "Rangpur Data Desk." It began as a Facebook page analyzing Bangladesh Premier League football. After Abahani Limited Dhaka beat Sheikh Russel KC 2-1, I posted a thread showing Abahani's xG of 2.4 versus 0.8 and a PPDA of 8.7. The thread reached forty thousand views, and three BPL coaches asked for my spreadsheets. I immediately hired two interns to log every match.

The Rangpur desk was not a room; it was a promise — a promise to count what others ignored.

That promise pulled me back from football to cricket. In 2026, at forty-five, I built a PPDA model for the Russia World Cup. Before the final I published an analysis citing France's PPDA of 13.2 against Croatia's 9.8, predicting a 3-1 France win. France won 4-2. My post was shared twelve thousand times, and a European analytics site offered me a column. That is how I began writing data breakdowns in English.

In 2026, at forty-seven, with global sport halted, I pivoted to the Bundesliga's Project Restart. Analyzing Borussia Dortmund's 4-0 win over Schalke 04 on 16 May 2026 in an empty Signal Iduna Park, I showed Dortmund covered 118.3 km versus Schalke's 113.7, yet my model showed home advantage falling by 14 percent. That launched the "Ghost Games Index."

This journey taught me one thing directly applicable to cricket: measuring the truth of a field demands disciplined counting and honesty toward that count. Yet my base has remained Rangpur, because if football's data culture is mature in Europe, cricket's data culture in Asia is precisely as immature — and that is where the work matters most.

Hundreds of matches are played across Asian cricket every day. Of those, the internationally recognized ones are a handful. The rest — district leagues, age-group tournaments, club cricket — enter no central database. This piece is about that lost ledger and its analytical method. I want to show five specific places where Asian cricket's data is systematically lost, and in each, demonstrate what a familiar metric actually measures.

1. The autopsy of strike rate

In Bangladesh's domestic T20, an opener's strike rate is 138. It doesn't sound bad. But when I began ball-by-ball logging at the Rangpur desk, I found something odd: roughly 40 points of that 138 came outside the powerplay, in dead overs when the result was nearly settled. In the hard overs, when more than eight an over was needed, his strike rate collapsed to 97.

That gap is the autopsy of strike rate. A single strike rate erases every context of a match — how many overs remained, how many wickets had fallen, whether the opposition's best bowler was operating. The industry treats the number as proof of a batter's ability, when it is really a context-free average. Here lies the first trap of accounting: the cleaner an average looks, the more information it hides.

I recommend a simple metric called "pressure-adjusted strike rate": count only the overs in which the win probability sat between 25 and 75 percent. The batter who survives that narrow window is the true match-winner. In Bangladesh's national side, Shakib Al Hasan's value is clearest exactly in that window — he keeps the scoreboard moving in hard moments, which a raw strike rate can never show. With Mushfiqur Rahim the picture inverts: his overall strike rate often looks middling, yet in the last ten overs, as wickets fall, his pressure-adjusted number leaps.

Recomputing this needs no big technology. A scorebook, an over-by-over table and patience — that is enough. The problem is that nobody invests that patience, because its output is not flashy enough for television. Where a number cannot be made to look pretty on a graphic, no investment follows. This innocuous-looking truth is the first cause of Asian cricket's data hollow.

2. The invisible value of the dot ball

Bowling economy rate is one of cricket's most deceptive numbers. A bowler's economy of 7.2 means what? How many dots, how many boundaries? Economy averages those distinctions away, and right there the match's story vanishes.

Take an example: two bowlers share an economy of 7.2. The first concedes four dot balls an over, then one four. The second concedes six singles an over. The first builds pressure; the second never does. Yet economy seats them at the same table. In T20 this gap often decides the result, because when pressure accumulates, a wicket arrives the next over — but the credit for that wicket goes to a different bowler's column.

In domestic cricket I calculate a "dot-ball pressure index" — what percentage of balls were dots, and in which overs those dots fell. A dot in the powerplay and a dot in the death overs carry different weight; one dot in the final two overs equals two in the first. This simple correction reveals whether a bowler is truly controlling a match or merely balancing a number.

In Pakistan's domestic Quaid-e-Azam Trophy the distinction is striking. Two left-arm pacers bowled with identical economy, yet one ranked in the top five of the dot-ball pressure index and the other at the bottom. National selectors ultimately decide on economy, and so the second gets picked first. The value of a pacer like Shaheen Afridi is understood precisely through dot balls, because his best spells sometimes end with only one or two wickets while he dictates the match's tempo.

There is a larger lesson here: a wicket is one number, pressure another. A bowling statistic that counts only wickets does half of cricket's work. A statistic that counts pressure earns no credit, because pressure has no place on a scoreboard.

3. The catching-efficiency trap

Now to fielding. "Catching efficiency" appears in almost every analysis — what percentage of catches were held. The problem is that this number does not count how hard the catches were, and right there the result flips.

A side that gets no easy catches will show an artificially high catching efficiency. Conversely, a side whose fielders face more difficult chances will see its number drop — even if it is the more skilled. The number measures the type of opportunity, not the quality of fielding. In Asian domestic cricket, slip catchers often take two or three hard catches, and one dropped sitter drags their overall rate down — a sick yardstick.

In domestic matches I use a simple classification: routine, medium, hard. Then I calculate catching efficiency only on routine catches, and separately show the success rate on hard catches. The picture that emerges from the two numbers often contradicts the single conventional figure. For one district side I found a routine catching efficiency of 92 percent — excellent. But their hard-catch success was only 18 percent. Yet that side had been praised for "superb fielding," because nobody counted the hard chances.

Here lies the trap of metric reification. I fell into it myself — I once flagged a domestic side's fielding as top-tier on a single number, then watched the ball-by-ball footage and realized they had faced almost no difficult chances. The scorebook said one thing, the field said the opposite. The ledger corrected me, and that correction is my most valuable lesson.

4. Bureaucracy across the border

This is where the distance between my birthplace and my workplace becomes useful. Born in Pakistan, working in Bangladesh, this dual position has made one thing plain: cricket's data is not merely about bat and ball, it is about administration. Which performance becomes visible and which stays uncounted is decided in large part by board paperwork, contracts, media attention and visa policy.

An example: if a young pacer travels across the border to play a domestic league, his performance often fails to land fully in either country's central records — in one record he is a guest, in the other he is absent. His career picture never becomes complete. A player who plays in two countries has his statistics scattered across two ledgers, and nobody opens both at once.

I call this gap "cross-border cricket bureaucracy." A player builds an international career right through that gap, where no one fully counts his labour. Scouting decisions therefore often happen by accident, not by system. A batter like Babar Azam is visible because he stands on the central stage; but if someone across the border carries the same talent, his performance may remain forever confined to a local scorebook.

The most cunning form of this bureaucracy is the contract and free-agent market. Large signing-on fees for free agents are often kept outside the accounting, because they slip past scrutiny more easily than a transfer fee — on paper it is not a fee, so there is less verification. Here the gap between money and truth widens, and that gap distorts a player's valuation.

5. The lost ledger of district cricket

Finally, back to that scorebook. In the Rangpur desk's first two years we logged roughly two hundred district and age-group matches — handwritten scorebooks, details heard from local coaches, sometimes interviews. In this work I followed one fixed rule: every number must carry a source, a sample size, and a date. If a claim is sourceless, it does not enter my ledger. This strictness is what keeps the Rangpur ledger separate from rumour.

From those two hundred matches one thing kept surfacing: the best performances are often the least seen. Because boys in big academies stand in front of a camera every match, while those playing in districts have no footage of their balls at all. The camera decides where talent lives, not talent itself. This truth is Asian cricket's largest uncounted ledger.

I have built a rule here that I call the "rule of counting": a match without a scorebook must never sit at the centre of analysis, however flashy its story. Because stories are cheap, scorebooks are scarce. I would rather chase those scarce scorebooks, because that is where unknown talent hides.

The correction: correlation is not causation

Now a caution I give myself again and again. More data does not mean better decisions, and correlation is not causation.

Every simplification in this piece hides a trap. Someone could point to the correlation between catching efficiency and strike rate and claim that those who catch more win more — but here cause and correlation blur. Good sides get more easy catches because their bowling keeps the opposition under pressure. So catching may be the result of winning, not the cause. This confusion is today's biggest disease in cricket analysis.

Working with PPDA taught me this: PPDA does not measure pressing; PPDA measures a team's hype. In the same way, a single cricket number never measures a match's truth, it measures our attention. The analyst who recognizes this trap can turn data into a decision tool; the rest turn data into ornament, and ornament wins no matches.

The forward signal

So next time you look at a scorecard, ask yourself — the balls not written there, where did they go? I am looking for the next match's signal in exactly that gap: not strike rate but dot-ball pressure; not catching efficiency but hard-catch success; not stars but lost scorebooks. The ledger is open, the narrative is on notice — who responds first?