The Empty Column: The Cricket Data No Scorebook Logs

December 19, 2026. Adelaide Oval. India's second innings folded for 36 in 21.2 overs — the lowest total any team has made in 144 years of Test cricket. By next morning those three dozen runs were on every front page. That night I sat in my Kolkata flat listening to stump-mic recordings. The ground was empty, so all that survived was the bat, the ball's thud, and one distant voice. The scorecard holds every number from that evening — eleven names, 21.2 overs, the count of fours and sixes, the fielders who took the catches. One column stayed blank. How many of those deliveries landed on a bowler's ankle in a way that kept his name off the team sheet for six weeks is recorded nowhere.

Cricket has every digit of its score and no account of its players' bodies.

In sixteen years this sport has moved from a scorebook to a server. DRS arrived in Tests in 2026, Hawk-Eye began measuring the ball's path in centimetres, pitch maps and wagon wheels became broadcast furniture, and in 2026 the IPL's Impact Player rule accepted that more than eleven people can play a match. Every ball now carries coordinates; every shot a speed; every spinner's delivery a revolution count. I have watched this game from the ground and from the edit suite for forty-nine years, and the pile of data is real. It cannot be waved away.

Auction and transfer season has become the same festival of numbers. Purse, base price, sold price, retention deductions, Right to Match cards — three days of live arithmetic, and everyone chases one figure: what a man went for. That number is freely available because it advertises both the board and the franchise. No franchise publishes what it paid for a fast bowler and which clause of the contract covers the state of his knee. In journalism this is elementary: a figure given away free usually serves the advertisement, not the business.

Consider the three columns that hold the most expensive information and get filled the least.

The first column is the body. Rishabh Pant's car accident was on December 30, 2026. He returned to competitive cricket in March 2026, through the IPL — fourteen or fifteen months. That was a rare case where the severity could not be hidden, because a hospital, a police report and public pressure all existed at once. The normal case is the inverse. A board or franchise bulletin says: week-to-week assessment. That phrase is not medical, it is communications. Its translation is that the report will keep moving. The rate at which tissue heals, the stage of physiotherapy, the loading schedule — none of it reaches an ordinary reader. So when a bid is made in a transfer window, buyer and spectator stand in the same dark.

The second column is the role. A heatmap shows where deliveries landed, not which over the bowler was bowling. A quick sending down four overs with a dew-soaked ball in the seventeenth and a teammate sending down two with the new ball in the sixth can glow identically on a graph. An opener's powerplay strike rate does not say whether he faced the new ball on a seaming pitch or farmed the spinner. A heatmap is a map, not a job description. Bids and selections are then made off that map, and something strange follows: the player whose role inside a system was clearest often goes cheapest in the market, because his numbers were the least luminous.

The third column is the ledger, and here two books open at once. In the franchise's book a player is an asset — value, contract, depreciation. In the player's book the same deal reads differently — security, retention, and the load placed on a body. When a franchise buys an all-rounder for a large sum and asks him for fourteen matches of bowling and batting, the contract looks like a win for both sides; the real accounting is settled two seasons later at the knee. And the knee appears in no balance sheet. The only honest use of this dual ledger is to write both sides on the page: what the player gained and what the franchise paid, and an explicit mark on what cannot be verified.

The other half of this counting concerns what Indian cricket coverage never even shows as missing. The Ranji Trophy lives in the margins of the calendar, and the workload data of its fast bowlers lives in the same margin. The decades of the women's game that only became visible after 2026 were never measured while they happened. The bilateral series against Pakistan have narrowed to ICC events and Asia Cups, which means an entire diary-style of record has vanished. My habit is to count these absences. When I watched the Under-17 World Cup final at Salt Lake Stadium before 66,684 people on October 28, 2026 — England beat Spain 5-2 — nobody told me how many of those boys would still be in any record four years on. The final's score is permanent; most of their names are not.

Something odd happens here, and the piece turns at this point. When I took a clean eight-dimension analysis template and laid a recent report across it, every field filled with N/A. The format was not populated, the venue was not populated, the bowler's economy was not populated, the franchise ledger came back empty. My first reaction was that the template or the input was broken. Then I read it the other way. That blankness was itself a result, and it is the most honest result available about the cricket-data industry today.

An empty field is not an absence of information; it is information someone decided not to publish. A player's injury grade, the release-clause structure of a contract, the part of a retention negotiation that never went public — all three share one property. At the precise moment they matter most, twenty-four hours before a bid, they are least available. In commentary this is the old transfer-window law: the noise is loudest where the facts are thinnest.

The second thing the blankness tells us is about collective memory. We kept 36 — the number thirty-six, three dozen, the lowest Test total. Six weeks later it was overwritten in Brisbane when Rishabh Pant's unbeaten 89 on January 19, 2026 ended Australia's 32-year unbeaten run at the Gabba. Both events are true, both are logged, and both are faces of the same coin. But the rehab, the physio, the sleep and the pain of those six weeks sit in no scorecard. My Silence Archive project was built on exactly this: Number 36 waits in the silence of the stands, not in the scoreline. When I pulled the scoreboard and pushed the stump mic, I learned that the truest data in the game is not noise but duration — how long nothing happened.

So here is my practical filter for this transfer window, and all three questions point at the blank columns. If one name keeps surfacing in pre-auction chatter, ask who saw his injury grade and when. If a franchise releases a player, ask whether the reason is squad structure or a medical file. And when an agent says his client will be on the field in a fortnight, ask twice what the standard for healed is and who set it. The newspaper habit has been to treat a player's body as a by-product of his talent. It is not. The body is the first condition, and it has no column.

Looking forward, two things will decide whether this blankness survives. First, medical-disclosure clauses in contracts — whether a buying franchise gets access to a player's injury history before purchase, and whether that access falls inside the transparency rules. Second, the domestic and women's data base — until the Ranji fast bowler's ball count is public, workload management there runs on guesswork. There is a third, and it worries me most: the habit of the data reader. The bigger the pile of numbers, the more readily we mistake the scorecard for the game.

The decision is yours. Next time the final bid flashes on screen and the commentator calls it a deal that suits both sides, which column would you want filled — the one that says what he was sold for, or the one that stayed empty because nobody thought it worth recording?