Zero Information Points: How Cricket Loses Its Own Memory

Late afternoon in Khulna, rain arrived before the scorebook had a chance to dry. The players walked back to the clubhouse, water gathered in the empty stands, and on the match official's laptop a cold sentence appeared: zero information points. No ball count, no batsman's runs, no bowler's economy, no fielding map, no DLS calculation. The match happened. Its memory did not survive. I keep returning to the rain, because it knew the score before we did — and this time it erased the score itself.

For more than two decades I have watched cricket — from Khulna's domestic grounds to the Sher-e-Bangla in Dhaka, from World Cup floodlights to Qatar's air-conditioned stadiums. I have filled notebooks, and written the sound of human breathing next to the scorecard. But this was the first time I met a match that existed and yet did not exist in the ledger of analysis. The question is not simple: what exactly did we lose — a result, or a memory?

Cricket is no longer just a game; it is an information system. Every delivery is now encoded — the bowler's pace, line and length, the batsman's shot zones, the fielder's position, even the humidity in the air. ICC rankings, format-specific statistics, strike rate, economy, situational splits, home-and-away breakdowns — together these form an enormous pipeline. In the first stage of that pipeline, a match is broken down into information points; in the second stage, deep analysis is built on top of those points. So however deep the analysis, its foundation is the first-stage information points. When the information points are zero, the analysis is zero — this is not a philosophical remark, it is the hard truth of engineering.

Twelve years in this profession have shown me that truth again and again. In 2026, while a student at Khulna University, I started a page called Pitch Poetry; the first long piece was on Sheikh Russell KC versus Abahani Limited Dhaka, a 2-2 draw — Rubel Miya's 78th-minute equalizer and 1,200 rain-soaked fans. That piece taught me that the scoreline is not the end of the story, but the beginning. In 2026, at the Russia World Cup, when France beat Argentina 4-3, I wrote "The Boy Who Ran Through History," focused on 19-year-old Kylian Mbappe's 64th- and 68th-minute goals; the piece was shared 8,000 times. Those two experiences taught me a habit — to carry a notebook to every local match, and to write the sensory detail of rain, breath and silence before the scoreline.

Later the page was rebranded BDCricTime, a hobby account turned professional cricket portal. The perspective changed, but the notebook habit stayed. Because I know a database cannot count certain things.

The information economy has another side. Broadcast rights, franchise valuations, player salaries — these calculations rest on visible performance. The game that reaches television accumulates data; the game that does not is priced at zero. So information discovers a player on one side and makes him invisible on the other. That is the natural outcome of a market, but a catastrophe for cricket's memory.

This is where the real question sits. When a domestic match is washed out by rain, when the DLS calculation does not reconcile, when the scorecard file is never submitted — the pipeline says there is no information. And yet the match happened. A bowler may have sent down the best yorker of his life with that wet ball, and no one saw it. A batsman may have stood unbeaten on 47 off 92 balls, and it never entered a ranking. A young fielder may have thrown himself near the boundary for a catch the cameras never caught. This invisible cricket is the bloodstream of the domestic infrastructure in Bangladesh and South Asia. Most of our game's labour lives here, and almost none of it ever becomes an information point.

Consider a young left-arm spinner. In the Khulna league he may take thirty wickets in a season, but not one of his matches is broadcast, no one measures the pace of his deliveries, and his footage never reaches a franchise scout. And yet countless stars in cricket's history have risen from exactly this dark corridor. Without data, that rise cannot be explained; it can only be called sudden. That word, sudden, is really our confession of incomplete data.

In my view, cricket's memory does not live in the scorecard; it lives in unlogged labour. What the data pipeline calls zero is in fact the biggest truth of our game. Because the pipeline asks how many runs, but cricket asks how, for whom, under what conditions.

I think of cricket's record book as a kind of ledger — each innings a block, each record an entry. But the core promise of a blockchain is immutability; cricket's ledger has none. Here blocks are lost, entries are erased, and nobody notices. Zero information points is that unwritten block — the one whose hash no one ever calculated.

The second point is subtler. An information point is not merely a number; a context clings to it — format, venue, weather, the behaviour of the pitch. Test, ODI and T20 data can never be mixed; that is the first rule of analysis. But if the format itself is not identified in the first stage, then format analysis is impossible in the second. That sounds technical, yet its human meaning runs deep: a match whose format is never recorded has, in the eyes of history, been played in no format at all.

And this is where rain comes in. I have always treated rain as cricket's first analyst. Before the first ball, rain tells you how the pitch will behave, who will win the toss, whether the spinners will matter, how Duckworth-Lewis will shift the numbers. When the rain falls, you grasp how much labour, how much preparation, how much expectation was silently cancelled. The greatest loss of a rain-abandoned match is not the result — it is the possibility that never became an information point.

The third layer is silence. An empty stadium still breathes, and Coman — Kingsley Coman, the former PSG academy boy who gave Bayern Munich a 1-0 win over PSG in the spectator-free Champions League final at Lisbon's Estádio da Luz on August 23, 2026, scoring the only goal in the 59th minute. I was watching alone in my Khulna flat. The sound that was missing after the goal — the roar of the crowd — was the loudest thing in the room. I wrote a piece called "The Silence Before the Header," about absence, echo, and the zero figure in the stands. That night I understood that zero, too, can be an information point — if you know how to count it. But our pipeline does not; to it, zero means nothing.

The fourth layer is people. The Euro 2026 final in 2026 — Italy 1-1 England, Italy winning 3-2 on penalties. I wanted to write about Giorgio Chiellini's 90+2 smile, about Bukayo Saka's missed spot-kick; but the racist abuse that followed drained me. I withdrew to Khulna for two weeks. Then the 2026 Qatar World Cup final — Argentina 3-3 France, 4-2 on penalties, Lionel Messi's goals in the 23rd and 108th minutes, Mbappe's in the 80th, 81st and 118th. Then Enzo Fernandez's £106.8m transfer from Benfica to Chelsea, on an eight-and-a-half-year contract. The transfer window is a confessional where numbers hide the names. That experience taught me that protecting an athlete's dignity is an ethical duty of analysis, and that fees and contract years work best as the cold counterpoint to World Cup emotion.

Injury news belongs to this system too. Week-to-week assessments are often the language of a PR team, not medical truth; sometimes a return timeline is set by commercial need rather than cricketing need. Those headlines look like information points, but a context hides inside them.

Now to the uncomfortable truth no one in the data age wants to say aloud. We assume that the more complete the data, the truer the analysis. The opposite happens: our obsession with data completeness creates cricket's greatest blind spot. What has no data, we easily mistake for what does not matter. Yet the most human parts of the game — the sweat of a domestic ground, a bowler's fear before the rain, the wait of a spectator in the fourth row — live precisely in that gap.

As an industry we have begun to accept a dangerous logic: what cannot be measured did not happen. Under that logic, investment in domestic cricket, the infrastructure of private leagues, and age-group scouting are always under-counted — because there the information points are few. Ask instead: who produces this data, who falls outside it, and who benefits? The answer is usually uncomfortable. An information system is a form of power; whoever provides the data gains power, and whoever does not has their story erased. This is why names like Coman's return as ghosts — even as the record book moves on, some names still wander the game's corridor, because their full story was never written down.

There is one more trap, dangerous for a writer like me: losing the evidence to excessive lyricism. Rain, the empty stand, Coman — these motifs pull so easily toward emotion that numbers and context can be buried. So I try to tie every lyrical passage to one concrete fact — a score, a minute, a date. Otherwise the line between memory and analysis dissolves.

From that rain-soaked Khulna afternoon I carried away one lesson — the game does not answer to us; we answer to the game. Perhaps next season more cameras will be installed, more data will accumulate, and the number of information points will rise. But as long as we keep erasing the zero-information match from memory, a part of cricket will remain forever unread. The question is no longer how many runs — it is whether we can learn to look at the blank scorecard the way we look at an empty stadium.