The Lesson of Zero: When Cricket's Data Stream Goes Silent

It is 11:48 p.m. The press box at Bengaluru's Chinnaswamy Stadium is nearly empty. Rain has stopped play, cameras are under covers, the tribune chairs folded away. Scorer Roshan Das sits in his chair — a pencil in his right hand, a tablet in his left. The tablet screen was running the live feed: an update every ball, runs, deliveries, strike rate, the count of fours and sixes.

Then the screen went to zero. Just one row — zero, zero, zero. No runs, no wickets, no overs. By then twenty-eight overs had been bowled, two hundred and thirty runs scored, three wickets taken.

Roshan looked at the screen, then at the paper scoresheet in his hand. Then he set the pencil down. Turning to me, he said, calmly, "The paper is fine."

That single sentence is the subject of this piece. We talk about cricket through runs, strike rates, rankings. But beneath the scoreboard there is another layer — the layer of information, where every number arrives through a human hand. When that layer goes silent, we feel it, and we realize how dependent we are.

Data never falls from the sky. The marriage of cricket and numbers is old. Since the first scorebook was introduced in England in the nineteenth century, the game has felt an unusual pull toward statistics. When Wisden first appeared in 1864, cricket became a sport whose memory is written on paper. Football survives on goals and tables; cricket survives on individual records — a player's runs, wickets, average.

But from the late twentieth century the information architecture changed. Data rose from the paper scoresheet into computers. Beside the scorer sat the data logger. In a single ball, perhaps five things were being recorded at once — line, length, pace, the angle of the batter's shot, the fielder's position. Technologies like Hawk-Eye, Snicko and UltraEdge arrived. Strike rate, economy, boundary percentage, dot-ball pressure — together they built a separate language.

In my twenty-seven years in journalism, one thing has become clear: the stronger this language became, the more invisible the people behind it grew. We see the data, not the labourer of data. Just as we see the midfielder's run but not the water carrier whose entire game is played without the ball. The beat is not in the drum; it is in the water carrier.

In this piece I want to talk about that invisible layer. And about the moment it suddenly goes empty — and how the emptiness teaches us most of all.

In 2026 I spent nine months with Bengaluru FC. I logged pre-season housing, eighteen ISL away trips on the team bus, one hundred and twenty training sessions. Coach Albert Roca's 4-2-3-1 pressing triggers are invisible on television. I watched Sunil Chhetri make thirty-seven decoy runs in one match — a 2-0 win over Mumbai City — purely to create space for Miku, who scored in the fourteenth minute. The scoreboard credits Miku with the goal. But beneath that goal, on paper, are Chhetri's thirty-seven invisible runs.

Since then I have kept a two-column notebook. On the left, tactical patterns; on the right, human consequence. This piece is about that right column — the one nobody usually reads.

Who the water carriers of data are. Picture an IPL match. What you see on the scoreboard is produced by at least four layers working behind it. The first layer — the scorer, recording every ball from the ground. The second — the data logger, tapping ball-by-ball information into a tablet. The third — the venue technician, keeping the Hawk-Eye and Snicko feeds alive. The fourth — a coder or analyst in a distant office, verifying the feed before it reaches the broadcast.

None of these four appear on screen. But if one of them slips, the whole broadcast, the fantasy leagues, the betting markets all tremble. A data logger I know works at two in the morning, because a European league's match begins at that hour in Indian time. He told me, "When we err, nobody forgives. When we get it right, nobody notices."

I have heard that sentence many times — from goalkeeper coaches, physios, scorers. It is the universal rhythm of service labour. And the right side of my two-column notebook is filled with exactly that rhythm.

The habit of seeing the person behind the number. At the 2026 World Cup in Russia I was fortunate in an unfair way — one of three Indian women in the mixed zone. In the semi-final, France beat Belgium 1-0. I was watching N'Golo Kanté. He ran 11.3 kilometres, made five tackles and three interceptions. His name was beside no goal on the scoreboard. But without the spaces he created for Pogba and Mbappé, the story of the match is incomplete.

That night a male colleague told me, "Women don't understand tactics." I did not argue. I simply filed a minute-by-minute tactical annotation alongside the match report — who stood where in which minute, which pass opened which gap. France beat Croatia 4-2 in the final. My point was proven in numbers, not in assertion.

That experience taught me a habit that sits at the centre of today's subject: not claim, but verification. Not who said what, but who did what. And to see that, you must go to the person behind the number — to the room where the number is made.

When a metric becomes scripture. Here lies the real danger. We love data because we believe data tells the truth. But data says nothing on its own; who is speaking, and to what end, decides its meaning.

I have long been suspicious of 'expected goals' (xG) in football. Cricket has produced the same kind of thing — 'expected runs', projected scores, win probability. These are not bad metrics. They turn bad when used as predictions of the future. No model can say in advance what a ball will yield, because the model does not know how much the batter's knee aches that afternoon, how damp the pitch is, or which way the wind blows.

Of the thirty-seven decoy runs I watched in Bengaluru in 2026, not one appears in any 'expected' model, because they were not runs — they were the creation of space. A metric measures the shadow of an event; it does not measure the decision behind the event.

The ledger of data and the broken node. Cricket's information system is, in fact, a distributed ledger — and this is now almost literally true. Each venue is a node, each scorer writes an entry, each logger verifies it. If one node fails, the others cross-check and recover the truth.

That is exactly what happened that night. The tablet's node went blank, but Roshan's paper node held firm. Cross-check two nodes and the truth survives. And here lies the core lesson of any blockchain-like information system — an empty return and a false return are not the same thing. An empty ledger is honest; a fabricated ledger is treacherous.

In my journalism I try to follow this rule. I do not publish unverified information, and if I cannot verify it, I leave it blank. Writing a zero is hard, because readers think you do not know. But a blank is far more responsible than an error.

Consent first, data later. This information economy has a dark side rarely discussed. Players' bodies, moods, injuries — all become data. Hawk-Eye measures the ball's pace, but nobody measures how hard it struck the batter's bone. Fitness data, sleep tracking, heart rate — who owns all this?

During my time at Bengaluru FC in 2026 I set a rule — I would not publish details of a player's injury until the player himself consented. Because an injury is the player's property, not the club's advertising material. This slow, cautious method earned me the dressing room's trust, and that trust brought the 2026 World Cup accreditation.

In the 2026 Goa bio-bubble this rule became even more urgent. When the world was shut, stadiums empty, cricket's information was also half-incomplete. I wrote that an empty gallery does not mean less information — it means a different kind. Echoes, the sound of the pitch, players talking among themselves — these were being gathered outside the scoreboard.

The moment the data goes silent. Back to Roshan's room. After the feed went to zero, a small game began in the press box — who would first say why it had failed. Someone blamed the satellite, someone the server, someone a software update. Some simply said, "Perhaps the match never happened."

That last remark is astonishing — yet this is exactly what we do in the absence of information. Without data we either imagine, or leap to a conclusion. And here lies the greatest risk of an information system: many systems mistake an empty result for 'no problem at all.'

I have seen this error repeatedly in my journalism. If a team wins three matches, we say it is in form. But its data feed may have had gaps — perhaps in two matches the opponent's key bowler was absent. The gap we do not see is the one that deceives us most. Honest use of information means admitting these gaps, not hiding them.

Commercial data and community data. There is another layer of the information economy, not directly tied to play but transforming the game. In the past two decades, most names that have appeared on cricket shirts are global brands — careers, betting, electronics. They have no relationship with the local community of the ground. They want data — exposure and return on investment.

But a club's real information lives in the neighbourhood around it — in coaching camps, school teams, street cricket. My fear is that the more international data flow arrives at a club, the less attention goes to that local information. The community that made the club big now has data that reads as a bad number on the balance sheet.

On the Bengaluru FC bus in 2026 I felt this contradiction. The team was winning, the brand growing, but those who turned up at pre-season camp to feed balls were in no media. Just as in the world of data the coder is absent — the story is only the feed.

Now to the central argument. What is seen from outside differs from the truth within. The outside assumption: more data means more truth. So the more data-dependent cricket becomes, the more accurate. We believe the more digital the scoreboard, the more transparent the game.

But the inner truth is the opposite. The more data grows, the more invisible its labourers become. And when the labourer becomes invisible, verification is lost. What the zero screen showed us that night is that the smarter the system, the greater its capacity to break — and that after the break, the truth is held by that ordinary sheet of paper nobody looks at.

And the second misconception: zero means nothing exists. But zero is really a question — where did the information go? Asking that question is journalism. Between an absence of information and an admission of that absence lies the real work of cricket journalism today.

A sentence I have heard many times. Data loggers, physios, scorers — the same sentence on all their lips. When the work is right, nobody notices; when it is wrong, everyone knows. This is the silent punishment of service labour. And my job is to keep account of that punishment — in the room where there is no gallery, no camera, only a pencil and a tablet.

In 2026, when responsibility for cricket's digital and media affairs came to my shoulders, I understood one thing clearly: there will always be tension between verification and speed. Some want speed, some want precision. But a feed that is fast and a feed that is honest are not the same thing. I have always been on the side of the second.

And the third misconception: technology has replaced people. In reality technology has changed people's work, not ended it. Hawk-Eye measures the ball's pace, but the decision is still human. The system creates data, but verification is done by a pencil-wielding human who knows which number deserves suspicion. The bigger the system, the bigger the human — only less visible.

Direction. After Roshan's night I became more certain — cricket's data future will not fall to machines, but will rest on the bridge between machine and human. The more data arrives, the more we need someone who can ask: who wrote this number, why, and where did what was not written go?

What the scoreboard shows is a summary. Cricket's real story lies beneath it — on the paper layer, in pencil strokes, in the tired eyes of a coder at two in the morning. The beat is not in the drum; it is in the water carrier.

So the next time you see a live feed at zero, do not scroll past it. Ask — where did the information go, and who is the person who still holds the truth. Because sometimes the zero speaks the loudest.