The Overs the Scorecard Deletes: A Ledger of Bangladesh's Test Batting

That session in Chattogram is still taped into my notebook. 31 overs, 78 runs, two wickets. The next morning's report said: "Patient batting, the session belonged to Bangladesh."

I opened the ball-by-ball log for those 31 overs. 186 deliveries. 134 of them were dots. That is 72 percent of the balls from which the batter took nothing, or was forced to take nothing. The remaining 52 balls produced 78 runs — 1.50 per scoring ball.

What enters the scorecard as a "good session" enters the ledger as 72 percent silence.

I count that silence. Let the ledger breathe before the narrative does.

Method first, drama later

Method before drama — an old habit of mine. So three terms first.

Dot-ball percentage (DB%): the share of deliveries in a block from which no run came.

Runs per scoring ball (RPSB): total runs divided by the balls that actually produced runs. Not strike rate — strike rate quietly absorbs the dots into its denominator, and my question is precisely about those dots.

Dot cluster: eighteen or more consecutive deliveries without a single run.

Sample: the first two days of the first innings in 31 Bangladesh Test matches between January 2026 and December 2026 — 34,217 deliveries, hand-logged. For comparison, the same window across 24 India innings and 21 Australia innings, logged the same way.

One date worth holding onto. Bangladesh played their first Test in November 2026, at the Bangabandhu National Stadium in Dhaka, against India. Their first Test win came in January 2026, in Chattogram, against Zimbabwe. The stretch between those two dates is the longest phase of our Test adaptation. What I have seen from the stands, year after year, is not a shortage of talent. It is a shortage of rhythm.

Let me state the limitations plainly: the log is hand-made, single-logger, not independently verified. Every number below is a boundary of estimate, not a verdict.

The question is simple. Why does Bangladesh's Test batting break? The received answers are "technique", "mentality", "big-match pressure". None of them is falsifiable, and none of them is measurable. I was looking for something measurable.

Where the average stops, the variance begins

The first thing that fell out: Bangladesh's first-two-day DB% is 68.4. India's is 58.1, Australia's 56.7. The gap looks small, but this is an average over 34,000 balls — an average does not always lie, it is simply incomplete.

RPSB sharpens the picture. Bangladesh 1.31, India 1.62, Australia 1.71. So even when a Bangladesh batter scores, he scores slower than an Indian one. The problem is not the number of dots. The problem is the distance between a dot and a scoring ball.

The real fracture, though, is not in the mean. It is in the variance.

In my log, Bangladesh's session-by-session DB% swings between 51.9 and 89.3 — a spread of 37.4 points. India's spread is 21.6, Australia's 18.9. Bangladesh's sessions are either very good or very bad; the ability to stand in the middle is what is missing.

Now the dot clusters. Clusters of 18+ dots per innings — Bangladesh 2.4, India 0.9, Australia 0.7. And 61 percent of Bangladesh's total wickets fell within the eight overs following the end of such a cluster.

Hold the order in mind: cluster first, wicket second. Not the reverse.

So who carries these dots? This is where the role-adjusted calculation becomes unavoidable.

In the first two days, when Bangladesh are past 40 runs, the share of balls wasted at the non-striker's end is 38 percent. For India it is 29 percent. A set batter is at the crease, and still the strike is not turning over — an over may yield a single, and that single off the last ball.

Let me put it by role rather than by name. The batter who faces the most balls in a Bangladesh innings as the set man has an RPSB of 1.44 — but his non-striker-end waste rate is 39 percent. His innings looks sound on paper, while an entire over is being spent at the other end.

The scorecard does not count those overs. The scorecard counts runs, and so the runs that never came are deleted from the record.

Now a cross-market observation. The price the same batter commands at an IPL auction and the price he holds on a BCB central contract differ not because of skill but because of metric. The auction room reads strike rate, and strike rate hides the dots. A side that reads RPSB pays a different number. Which of the two is right? For pricing first-two-day contracts in my sample, RPSB's explained variance is 1.7 times that of strike rate. Small sample, but the direction is clean.

The stadium was not empty; the numbers were not empty. What was empty was our line of sight.

Not slow batting — unstable batting

The easiest reading: "Bangladesh bat slowly, so they fall over." It is comfortable, and my log does not support it.

In my sample, the relationship between session-level DB% and wickets lost in that session is weak — a Pearson coefficient of 0.21. There is no straight line from more dots to more wickets.

What does exist is something else: the relationship between the variance of DB% and wicket clusters is 0.58. The team breaks not from the quantity of dots but from their instability. One session at 52 percent dots, the next at 87 percent — that jump puts a batter on the wrong foot. Rhythm goes, defence tightens, and then comes the mistake.

That changes the question. The question tends to be "are our batters technically weak?" when it should be "why is our session-to-session plan over the first two days so unstable?" Defence when wickets fall, run-hunting when they do not; the middle setting is missing.

One more thing belongs here, and nobody writes it. The "prove yourself" pressure on a returning batter's first innings inflates that instability. When someone comes back from injury and makes 11 off 28, we write "slow, low on confidence" — yet the log shows his DB% in that innings was only 3 points above the team's average. The difference was not in the statistics. It was in the weight of expectation.

Limitations again, because otherwise this becomes a blog rather than an analysis. Hand-logged data, one coder, session boundaries defined with some discretion. The variance pattern is worth watching, not worth deciding on.

I am writing it down now

I am writing it down now, with a date on it: if Bangladesh's session-level DB% spread drops below 28 points in the first innings of their next Test series, I will take it that something structural has changed in the batting plan. If it does not, the conversation should move from technique to plan.

I count dot balls because that is what the scorecard withholds from us. The real events of a Test match happen in those empty overs — we only see the result afterwards. I count the silence between the balls.