The Innings That Never Started: Absence as a Variable in Cricket Analysis

Last season a Dhaka Premier League match was scheduled for me to watch at Mirpur. Twenty-seven minutes after the toss, at 2:40 pm, the rain arrived. At 4:50 pm the match was abandoned. Before I left the press box I opened the scorecard one more time — batting card empty, bowling card empty, not a single dot on the fall-of-wickets graph. Not one cell had been filled. I wrote roughly 3,800 words about that empty card that week, and it became one of the most-read pieces of the year on my newsletter, The Half-Space. Because an unplayed match is not an absence of information — it is a measurable zero.

Cricket is a data-producing machine. Six balls an over, one event per ball, at least three variables per event — runs, wickets, delivery type. A full Test match generates around 2,700 deliveries and far more decisions than that. At the 2026 World Cup in Russia I hand-coded 1,200 pressing sequences across 64 matches; in cricket I applied the same method to all 33 matches and 4,112 balls of the 2026 Bangabandhu T20 Cup. The numbers accumulate. But the real question is this: where no ball was bowled, what accumulates there?

Absence arrives in cricket in three forms, and all three are data. First, balls not bowled because of rain or bad light. The Duckworth-Lewis-Stern method is built entirely on that zero — a target recalculated from how many overs a side lost. Second, players who did not take the field — injury, suspension, selection. Third, spectators who did not sit down. The entire 2026 Bangabandhu T20 Cup was staged at Mirpur with zero crowd, from November 24 to December 18. Coding all 33 matches and 4,112 balls, I found that death-over wicket incidence for the designated home side fell from 38 percent to 24 percent. Silence, in other words, is itself a variable, and it has a pulse.

I understood this more clearly at Mirpur in August 2026. Bangladesh beat Australia by 20 runs there, and Shakib Al Hasan took 5/68 and 5/85 — ten wickets in all — in 34 degrees Celsius and 81 percent humidity. I filed the match report, then wrote a separate 4,200-word piece on how Bangladesh's bowlers survived 88 overs of thermal load. The Dhaka daily never ran it. Ten wickets in Mirpur taught me that a newsletter nobody asked for can still be a control group. Nine hundred subscribers arrived in eleven days, and I stopped opening articles with scores and started opening with load — overs bowled, minutes played, degrees Celsius.

The Duckworth-Lewis-Stern method is, in effect, a mathematical confession: that a match not played is still part of the match. The method was born after the 2026 World Cup, when rain-shortened games were being decided unfairly. In every revision — 2026, 2026, 2026 — researchers re-measured the value of zero overs. It is proof that cricket administration itself has finally admitted absence can be measured.

There is a methodological truth buried here. Every piece I write carries a conditions block — crowd, weather, calendar, travel — before any tactical claim. A tactic is a hypothesis; the match is peer review. And when the match itself does not happen, the review has to be conducted on the emptiness. I measure and date and source every one of my own numbers, even when that number undercuts my own argument. That is uncomfortable to admit, but it is professional.

In the Bangladesh context these zeros weigh heavier. When a senior player drops out injured, a name is not all that is lost — an entire tactical balance shifts. Selectors often treat that gap as personal misfortune and decide accordingly, when it is in fact a measurable hole. Succession in cricket should never be settled by sentiment; it should be settled by conditions and numbers.

But the gravest offence in analytics happens in the exact opposite direction — when information is missing, we invent it. Handed an empty dataset, many analysts refuse to admit they do not know; they fill the cells with guesses. The professional standard is the reverse: where there is no information, write plainly — insufficient information, cannot assess. That is not weakness, it is control. Analysis built on an invented team or an invented player is not merely wrong; it contaminates every decision downstream.

I saw this myself in my Kazan notebook in 2026. Across 64 matches I hand-coded, and when a sequence had a data gap I did not estimate it — I left it blank. Later it turned out those blanks showed me which teams stopped pressing as they tired. It was the zeros, not the complete figures, that told the real story.

The second danger is subtler — we treat absence as nothing. A rained-off day becomes a gap in the calendar; a player's injury becomes personal misfortune. In reality these zeros shape selection, tactical balance and memory. The 2026 silence was not an absence; it was a variable with a pulse.

I propose a simple but neglected practice: every series analysis should keep an absence log. How many potential balls were never bowled, how many selected players never played, what percentage of seats stayed empty. That log is itself a control group — only then do we know how much of a performance was context and how much was talent. At sixty-four, I still trust the anomaly more than the average, and the largest anomaly usually sits in the event that never happened.

I know this argument is unproven — 33 matches is a small sample, and the 2026 conditions cannot be repeated. The data that would falsify the model is this: if, once crowds return, death-over wicket incidence stays near 24 percent, the model is wrong — because then the cause was the ball or the tactics, not the crowd. I am ready to measure it.

At the next match, the next series, when you open a scorecard, count the empty cells once. Perhaps the answer you are looking for is hidden among them — an answer the full cells could never give. The question is not for today. The question is whether we have learned to measure the void.