The Null Packet: The Counting That Quietly Stops in Cricket's Data Room

The Null Packet

Nine forty in the morning. The grass at Pune's MCA Stadium still held dew, and two of the three chairs in the press box were empty. The scorer in the third chair had fourteen overs filled in his book. Six balls an over, a small mark against each ball, a 'W' against one, a little arrow against another where the ball had come off the edge. At the bottom of the page he had written in pencil: wind south-west, moisture on the pitch, will dry by noon. Cricket's most honest book is that one, and in it no cell is ever left blank.

Beside him a laptop was open on the same match, live. Score: 0/0. Overs: 0.0. Bowler: —. Batter: —. The commentary box carried one floating line: awaiting start of play. He refreshed three times. All three times the same empty frame came back. Then he picked up his pencil and logged the next ball as though nothing had happened.

A filled book and an empty screen, in the same room, about the same match, at the same moment. That morning there was no controversy on the ground, no hundred, no review. A server simply did not answer, and an eight-column template stayed alive. This is the most important passage in this piece, and it is the one no television channel has ever cut to. I have watched a thousand drills end; the ones that matter end quietly.

How the data room was built

Cricket was the first sport to keep its entire memory in a ledger — wickets, overs, catches, who dismissed whom, how much wind there was in which over. Until the end of the twentieth century that memory sat on paper, and to read it you had to walk into the same room I sat in that morning. Then came the ball-by-ball digital scorecard in the late nineties, then broadcast graphics, then ball-tracking, then fantasy cricket, and then the thing nobody had planned for: the auction purse. Today a single ball in a domestic match becomes four different products — the live score, the graphic, the fantasy points, and tomorrow's stat card.

There is a strange thing in this architecture that I have watched for twenty-five years. In the data world, an empty cell has no existence. If nothing happened, the scorer writes zero, or a dot, or 'absent'. All three are different and all three are information. In software all three look the same — a blank field. And once you drop that blank field into a template whose eight headings are already printed, the blank becomes 'analysis'.

My generation of reporters lived through this shift. We saw how a scorer's pencil reached the bottom strip of a television screen and came back to the same scorer as a 'feed'. The man who watched a ball leave the edge is now trying to read an edge-percentage graphic about the same ball. That is progress, and it is half-finished progress, because nobody built a language for the moment the feed stops.

Three games, three arithmetics

Cricket's largest technical truth is that it is three different games sharing one name. Test, ODI and T20 averages, strike rates, economy rates and strategies are not interchangeable. It sounds so obvious that people forget it.

Consider a fast bowler with a Test economy of 2.9 and a T20 economy of 8.6. Same man, same arm, same run-up. The first number says miser; the second says expensive. Both are right and both are worthless unless you name the format. A T20 strike rate of 180 is elite; the same 180 in a Test is absurd. A spinner's economy of 6.2 is excellent in T20 and, if it is per over in a Test, that bowler is out of the attack by lunch on day one.

There is a third layer that did not exist twenty years ago — the auction price. A bid is not a measure of a player's cricket; it is a measure of one franchise's need in one season. In February 2026 Rising Pune Supergiant bought Ben Stokes for ₹14.5 crore, the biggest bid of that auction. That price did not make Stokes the best cricketer in the world. It told you that one franchise had one empty slot and was willing to pay the most to fill it. Cricket's numbers and cricket's market speak different languages, and the worst errors happen when a writer puts both in the same sentence.

That is why the first step of any serious analysis is format. Decide which game we are discussing; only then does a number mean anything. A number without a format is a temperature without a unit — 'thirty-two' does not tell you whether to wear a sweater or switch on the air-conditioning.

What an empty packet looks like

What I saw on that screen was a null input. No content arrived, so the frame came back exactly as it was. The danger is not that content was missing. The danger is that the frame survived.

When eight columns look filled, the reader assumes eight things were examined. When every column says 'not available', the reader mistakes it for the analyst's honesty, when in fact it is the system's failure. The worst case is when that packet enters a scoring or ranking engine: 'not available' becomes 'no risk' silently.

Cricket taught me the lesson analytics needs. A scorebook has no blank spaces. If a batter scored no runs, you write zero. If a bowler did not bowl, you write 'did not bowl'. If rain stopped play, you write 'rain'. All three are different and all three are information. Zero is a datum; a blank is the absence of a datum. Printing both in the same colour is not a professional error, it is a professional dishonesty.

No signal is not the same as no risk. If I have no news of a bowler's injury, that does not mean he is fit. It means I have no news. Journalism has a cheap word for this — 'unknown' — and a better one: 'I have not asked yet'. The distance between those two is the whole job.

Kedar Jadhav's nets, and the story past the ledger

Based on my years of watching from the ground, the best cricket stories are found where there is no score. 2026. I spent the full season with Maharashtra's Ranji squad, every morning in the nets at the MCA Stadium. That year a twenty-two-year-old scored 865 runs at 54.00 — Kedar Jadhav. You can read that sentence and move on. I did not move on, because I had spent that season in the two hours the sentence does not mention.

After every net session he batted another forty minutes. No coach, no camera, no drill. Just a throwdown bowler and one ball he kept asking to be hit into his feet — the ball that troubled him most that season. I watched that practice at least sixty times. It never became a feature, because it never finished on any particular day; it thinned, from forty minutes to thirty to ten.

The scorebook could tell me he made 865 runs. It could not tell me what those runs were made of. I spent sixty mornings to find out. What I have is a ledger; what I do not have is the afternoon he walked away from that drill and told nobody why. The reader needs both. So do I. And above all I owe the reader the difference.

The keepers of the beat

We who cover cricket measure our beat by the players. Wrong measurement. The beat is measured by the people whose names never reach the highlights — scorers, umpires, net bowlers, physios, pitch curators, the men and women in the Hindi and Tamil commentary booths. One of them leaving is a bigger story than any hundred, and it never makes the front page.

I have counted. A scorer who has sat at one ground for thirty years is half that ground's institutional memory. He knows which pitch does not turn on day two, which umpire is slow to raise a finger, which batter hit a six off his first ball here six years ago. The day he retires, nothing trends. For the next three seasons people say the data from that ground is odd.

It is not only scorers. A curator who knows every block of his square is a strategic asset to a team. When he goes, the team does not lose the pitch's history, it loses everything but the pitch's colour. A net bowler who bowls from morning to evening, if he breaks down and leaves, sets a first-class batter's preparation back two steps in a week, and his name appears nowhere.

My plain view is that the healthiest indicator of Indian cricket is not the national team's ranking points. It is how many scorers changed in one Ranji season, how many curators retired, and who replaced them. That count tells you how many legs the game actually stands on. Nobody claps for the metronome, but everybody stumbles without it.

Counting the domestic calendar

The industry counts money. I count days. How many days in a Ranji season, how many net sessions in a week, how many physios with one team, how many chairs filled in a press box. None of it gets a graphic, none of it gets a debate.

It is easy and comfortable now to say the IPL hollowed out Test cricket. Twenty-five years on the ground tells me that charge is delivered to the wrong address. The IPL's money did not hollow out Test cricket in India. It hollowed out the floor below it — the floor where Ranji, Vijay Hazare and Syed Mushtaq Ali live, where a regional team's season hangs on one monsoon, where a middle-order batter plays six months on a forty-lakh season fee and tries his luck at the next auction.

That auction needs understanding, but it should not be read as a trading floor. When Rising Pune Supergiant put ₹14.5 crore on Stokes in February 2026, the loudest effect was felt the next morning in Pune's nets, where local players suddenly had trials at a franchise with overseas power and a hunger for domestic depth. An auction is a labour market as much as a rich man's game; it creates jobs and it removes jobs. The difference is that the jobs created get reported and the jobs removed do not.

2026: the lights came on and the listening stopped

2 April 2026, Wankhede. I was in the ground the night India won the World Cup. The noise that came out of that night was the loudest ever heard at an Indian ground. And my counter-intuitive read, the one I have defended for fifteen years, is that the lights came on and something else went out — the habit of listening.

For a decade of celebration, paying attention to the game's quieter signals felt like ingratitude. Ask in 2026 about the women's domestic structure and the answer was: we have just won the World Cup. Ask about the depth of the second-innings bowling and the answer was: we have the best team. Both statements were true and neither was an answer to the question.

Here I have to escape my own trap. It flatters me to say everything was better before, and it is false. Date-stamp it: in 2026 domestic cricket had almost no television coverage, the women's game had no payment structure, regional-language commentary barely existed, and a Ranji report was three lines on the last page. Today Tamil and Hindi booths are real professional places, the women's game has a calendar, and a domestic match streams. That is better, and it must be called better, or my whole quiet-signals argument becomes nostalgia with a microphone.

What changed after 2026 was volume — and with volume came a habit: believing only what is visible. What is not visible no longer has a place to stand.

2026: when a city sat down to wait with its team

May 2026. The IPL spot-fixing story broke, and the arrests with it. I was with Pune Warriors, and those three days were not ordinary match reporting. I spent them outside the team hotel and near the stadium gate, and I spoke to twenty supporters.

One was angry, one cried, one said he wanted to return his season ticket and would not. On the third day the city's fans held a support march. It sounds odd — a march for a sport facing a corruption charge. But the march was not for the team. It was for people who felt that something they connected with every evening had been taken from them by somebody else.

A fixed match does not sound different until you know the beat. That is the hardest thing I have learned. A fixed match looks entirely normal in a scorecard, because it was built to. The difference is in the pace behind a delivery, the wait before it, the field that player had never set before. Being on the beat means you stop watching the ball and start watching the four seconds before it.

I also learned that the anti-corruption machinery runs on a tempo of its own. When investigations orbit only big names and leave the small grounds, the small scorers and the small leagues alone, the machinery is hollow — because risk is always created where nobody is looking.

2026: a full crowd in an empty stadium

September to November 2026, the United Arab Emirates. I was with Mumbai Indians for the whole season. The stadiums were empty and the television was full. That was the season's most honest contradiction — a game whose entire appeal is a crowd's noise was played without crowds and remained the most watched cricket on earth.

I reported that season differently. In Pune there was a fifty-member Zoom watch party. They joined for every match, ran one chat thread, messaged each other at every wicket. I spoke to three of them in three cities. Their stadium was a home and their stand was a screen.

In November Mumbai Indians won their fifth title. That night I wrote about the players' isolation, about people who had spent six months inside a biobubble, and about a crowd that was not in the ground and was present at every ball. At the time I thought I was writing about a pandemic. Five years later I think it was a rehearsal.

A professional rule came out of it: treat the digital crowd as a source, never as the audience. The reaction on a screen and the reaction of a man in a seat are different things. The first is fast, the second is true. The first can be measured; the second can only be watched.

Asia's coverage and the lean of the pipeline

Back to that empty screen, because it has a political side nobody talks about much.

When a system is fed news of India, Pakistan, Sri Lanka, Bangladesh, Afghanistan or the Asian leagues and cannot extract content from it, the loss is not one story. The loss is that tomorrow's analysis, next month's index and next year's ranking get built on the same missing information. If one continent's stories keep coming back empty, that continent's cricket starts to look risk-free to the system. Not risk-free — invisible.

In twenty-five years the lean has always gone one way: where coverage is cheap there is more news; where there is more news the data looks reliable; and where the data looks reliable the money goes. The absence of a report on a Bangladesh domestic match is not just an editorial omission, it is an economic one whose cost shows up ten years later.

The same applies to labels. 'Cricket' and 'cricket-Asia' are different things. The first is a sport, the second is a postal address. When a system puts both in one field, two matches from two countries get weighed on one scale. It is the same error as putting a Test average and a T20 strike rate in one table: the numbers are right and the comparison is nonsense.

Counter-intuitive, but it has to survive the scorecard

The biggest risk in my trade is that people have decided I am the man who looks the other way. That badge is comfortable and it is dangerous. When 'everyone is looking in the wrong direction' becomes your default opening, you start turning even the truth upside down.

So I keep three rules. First, test the contrarian claim against the scorecard and the table before you commit; if neither supports it, it is not a claim, it is a habit. Second, when the loud story is right, say plainly that it is right. On the night India won at Wankhede, the loud story was right; there was no hidden meaning to hunt for. Third, my distrust of metrics is laziness dressed as principle. Twenty-five years of analysts winning arguments has made me flinch from numbers, and that is not good enough. So I keep a counting habit — sessions, spells, overs, net run rate — as rhythm, not proof. Numbers should serve the scene, not replace it.

And one last thing I must admit about myself. I talk to the people I cover, they like me, and I like them. That is access and it is a risk. A coach who calls me for tea knows his name will appear in my copy. My rule is simple: disclose the relationship in the piece, keep a written record of the conversation, and write the accurate sentence. If a friendship breaks on one accurate line, it was not a friendship. If it survives, it is stronger than before.

Do not romanticise the empty screen

Here I have to say something sharp about myself. When I first saw that empty screen, my first thought was what a deep symbol it was — the machine does not know, the man knows, the pencil tells the truth, the server lies. Very beautiful. And completely wrong.

The screen was no conspiracy. It was a fetch failure — a server that did not answer, a page that did not render, a token whose date had passed. Making a mystery of it is my habit and not my job. While a technical fault is turned into poetry, the actual repair does not happen. The repair was somebody reading a log, counting characters, asking for the source again.

That is the lesson I will repeat in every piece: the most important line in any report tells you what the report does not contain. The reader has a right to know which data the analyst had, which he did not, and why he chose silence about the difference.

What to watch next

Tomorrow morning I will sit in that press box again. Three chairs, two empty. The scorer's book will be full. There will be a screen beside it, and I will not look at it first — I will look at the book, because Ranji taught me that the truth is the last thing you find on the scoreboard and the first thing you find in the room where the pencil is moving.

The people who run this game have a new duty nobody trained them for: to say where their data is empty. The scorer has done that job for a century without training, on his own wits. Now the software has to learn the same thing — the difference between zero and nothing.

The beat was there before the noise; I only learned to count it.

And one question I will put to every editor I work with: when your morning feed comes back empty, will you publish it, or will you write that the system did not answer today? Because if you choose the second, then tomorrow that empty space becomes a statistic — and nobody will count it.