The Balance Sheet of Zero: The Cricket Data That Never Gets Recorded

The file was named simply — cricket_world. Inside it were eight sections, a risk matrix, a technical glossary, and in every single field the same sentence: "N/A — insufficient information, cannot assess."

On a Monday morning in Pune, that file was open on my desk. It was a report that was structurally complete and completely empty. No score, no player, no venue, no date. The pipeline that should have produced it had not failed loudly; it had quietly returned a null schema. There were no cricket facts inside it. There was only the shape of cricket.

I did not delete it. In nine years of working with cricket numbers, my most expensive mistakes have not come from data that was wrong. They have come from data that was missing, and from the story I put in its place.

February 2026. The IPL auction was running in Bengaluru and I was sitting in a room in Pune with Excel open. My model had runs and wickets per crore for the 2026 and 2026 seasons, typed in by hand from Cricbuzz scorecards. Rising Pune Supergiant paid ₹14.5 crore for Ben Stokes, the most expensive overseas buy of that auction. My model had ranked Stokes ninth.

Stokes was Player of the Tournament. Rising Pune Supergiant lost the final to Mumbai Indians by one run in Hyderabad.

I published a post-mortem — "Why My Model Was Wrong About Stokes" — and reweighted for death-overs impact and close-match batting. But the real lesson was not about weights. The real lesson was that my spreadsheet had a column with no numbers in it: the dressing room, the pressure, the role that never appears on a scorecard. I had filled that empty column with my own narrative.

Since then, every report I write opens with a short paragraph: how this could be wrong. That empty file showed me the same habit again, this time at the scale of an entire industry.

There is an odd thing about cricket's information economy: the things that get recorded are not valuable because they are recorded. They are recorded because somebody has a reason to sell them.

On IPL auction day, every bid has a camera on it, every purse is counted live, every retention and every Right to Match is a graphics desk's main task for the day. In that same week, a Ranji Trophy match often ends in a single line — "three wickets fell on day two." That gap is not technical. It is commercial. Where the broadcast window exists, the data is dense; where it does not, the data is absent. And absence is not priced.

I understood this first by looking at my own model: I had less than a tenth as much data for domestic cricket as I had for the IPL. I had built a spreadsheet to price the auction, and it priced my assumptions instead.

At the 2026 World Cup I logged every restart in all 64 matches in Russia — corners, free kicks, throw-ins — with first contact, second ball and time-to-shot, live in a Google Sheet. England's rehearsed corner routines and Croatia's three consecutive extra-time knockout wins told me that the dead-ball phase is a separate sport hiding inside the sport. In August I wrote that India's 1-4 Test defeat in England was a restart problem: the first fifteen overs were cricket's corner kick, and India kept losing first contact.

That same year my attention moved off the play and onto the paperwork. Which metric crosses which format barrier, which number reaches which report, and which fact never reaches any report at all. The empty file was the cleanest specimen of that question I had ever seen.

The most dangerous number in cricket is not the one that is wrong. It is the one that is missing, with a story poured into the space it left.

Zero has a balance sheet too. In April 2026 my internship at a Pune sports event-management firm was cancelled in a single email. During the shutdown I started logging crowds instead: IPL 2026 in the UAE, three empty venues, sixty matches. Mumbai Indians won a fifth title.

That was the season home advantage was priced at zero. The column in every model marked "home ground" sat empty for the whole tournament. And that was the most interesting part: the product did not collapse. The broadcast ran, viewers stayed on television, the fantasy market kept moving. The thing we treat as half of cricket's economy — the home ground — was removed, and the structure did not fall.

On 19 December 2026 in Adelaide, India were bowled out for 36, their lowest Test total. Three weeks later at the Gabba, India beat Australia.

The story that formed between those two results was a story about character. The story that did not form was a story about phases. I never treat 36 all out as an innings. I break it into four blocks: the first six overs, the next twenty, the last ten, and the half hour in which wickets acquire a price. In Adelaide, India had lost two wickets inside the first block and their run rate declined in every block after it. At the Gabba the reverse happened — the pressure India built in the final session of day four is visible in a block-by-block count, not in a headline.

None of my models for that series could have told you in which over, for which batsman, the hands would shake because of injury and inexperience. That is the thing the model cannot see, and every time it deserves a paragraph of its own.

Format is a wall, and that was the empty file's largest lesson. Its domain label read cricket_world when the specification required exactly Cricket. That small slip invalidates the entire analysis, because the next question is always: which format? Test, ODI, T20, or The Hundred?

With no format there is no meaningful metric. The hunger of the first ten overs in a Test and the hunger of a T20 powerplay are not the same thing, even when both get labelled "the start." Death-over economy is a measure of performance in T20; in ODI those same overs are often the ceremony of a result already decided. A DLS-revised target, an umpire's call on DRS, the two-new-ball structure — these are the grammar inside a format. Carrying a number from one format into another is speaking the same sentence in a different language.

That is why the report wrote off its very first section: format could not be established. That was not laziness. It was the only honest answer available.

When you do not have the format, you do not have comparison; when you do not have comparison, you do not have an opinion — you have a mouth.

Now the uncomfortable part. The report's template carried a rule: a minimum of three analytical conclusions and two hidden-information items per dimension. With nothing inside, that rule became pressure to fill.

That pressure is cricket media's daily work. Injury news arrives with no sources, so "the team management is unhappy" gets written. No briefing emerges from the selection meeting, so "the young player may be rested" gets printed. No franchise opens its purse at an auction, so an analyst turns an estimate into a report.

One of the expensive forms of this pressure sits around NOCs and retentions. Whether a board has withheld a No Objection Certificate is a documentary fact; in its place, a story about "tension" runs instead. ACU monitoring, slow over-rate sanctions, the WTC points table — the facts in all of these are public, yet the estimate still outruns them in coverage, because the estimate is fast and the fact is slow.

I apply this rule to my own work now: if a section can only be filled with guesswork, leave it empty and state why it is empty. A reader who returns after reading "we don't know" is worth more than one who leaves carrying something false.

And here I had to correct another habit. While writing this, I was about to declare that Indian cricket suffers from an information crisis. The people inside the system already know this — the regional-language desks, the reporters who cover Ranji, the scorers who sit through domestic matches. They write daily about where the data is not. Their voices carry less because their audiences are smaller, not because their judgement is weaker.

The empty file showed me what a Ranji reporter has known for years: the system records what can be sold, and everything else stays in somebody's private notebook.

Which is where my own kill-list has to be applied to my own argument. For a few years now I have had a set piece: "absence has a balance sheet too." The sentence is true and the sentence is dangerous, because it turns every empty dataset into a story.

The truth is that file was not a mystery. It was a plumbing defect. The extractor did not throw an error; it returned a null schema, and the next stage accepted it. There is no deep cricketing truth in that. Sometimes zero is just zero.

My instinct is to romanticise absence — the empty stadium, the cancelled internship, the IPL without crowds. Those genuinely mattered. But not every time. Sometimes a stadium is empty because the ticket price is wrong, and the fix for that is a ticketing system, not an essay about the future of cricket.

So if this whole episode yields one thing, it is this: presenting missing data as a story is as serious an error as treating missing data as zero. Both leave the reader without what should have been in their hands — the fact and its boundary, together.

I have filed a copy of that report in my "not yet priced" folder. That is where I keep the stories I killed too early. Every quarter I open it again. Some are dead. Some have new data. And some contain nothing but an empty field, with a note underneath: there was nothing here, and that is also a fact.

What I am tracking hardest this season is not a score. It is how much data gets recorded for matches played outside the broadcast window. If ball-by-ball domestic records become public within the next two years, the auction models will not survive in their current form — and on that day we will learn how many players we under-priced simply because their match fell outside a camera's range.

The question is not how much data cricket has. The question is which data cricket has decided not to record — and whose interests that decision served.