The Frozen Table and the Invisible Ledger: Who Really Keeps Cricket's Record?

The table froze in the last week of March 2026. The points table that used to move every night suddenly went still, and nobody knew for how long. Sitting at home in Barishal, I kept refreshing the live scorecard; the page loaded, but the numbers would not move. Then a message arrived from our fan group: 'Isn't the table going to update?' Twenty replies below it: 'We'll write it down ourselves.' That night I added a new column to my notebook — who is actually keeping the record. Years later, mid-tournament, the same scene returned. The live data feed vanished for a few minutes, and Twitter, group chats and Messenger had already written the score. Some were faster than the official feed. This is cricket's least-discussed truth: the game is played on the field, but it survives on paper — and that paper is not always official. Cricket's greatest asset is its information. A ball, a run, a dismissal — these accumulate and become history. Don Bradman's Test average of 99.94 (retired 2026), Sachin Tendulkar's 100 international centuries, Muttiah Muralitharan's 800 Test wickets — these are not mere numbers, they are cricket's memory. But the system that stores them is not as solid as it looks. Behind every ball on the field is a scorer. He writes it down — runs, overs, extras, wickets. From that scorebook the data rises to the board's server, then to the statistics agencies, then spreads through broadcast, apps and newsrooms. One error, one missing over — and the whole chain shakes. I have seen a domestic match where the score-sheet and the live app disagreed by runs for three days; in the end nobody decided which was true. In Bangladesh the matter is more complicated. Many domestic matches never get a full scorecard online at all. The Dhaka Premier League, the First Division, small divisional tournaments — here data lives in notebooks, in someone's memory, and in a few phone screenshots. For national-team games, every run of Shakib Al Hasan, Tamim Iqbal, Mushfiqur Rahim or Litton Das is online; but at the lower tier where these stars are born, the data is nearly orphaned. I once touched a paper scorebook that had got soaked in rain. The pages had stuck, some figures had smudged, and nobody remembered the runs of two overs from that match. An entire over of play was lost to a wet page. In the digital age that seems impossible, yet at the lower tiers it is daily reality. When cricket stopped under the pandemic in March 2026, not only matches halted — the flow of data halted too. The table froze, and with it the scorecards, the forms, the statistics. That period taught me how centralised cricket's information system is. Stop the game and the broadcast stops; stop the broadcast and the app stops; stop the app and the data stops. But fans do not stop. In our group, the boys were scanning old scorecards, collecting old news clippings, arguing over who scored how many in which match. The official system was frozen; the fan archive was alive. My blogging life actually came from this Facebook group into the newsroom — the table had frozen, but the players and the fans were writing their own minutes. The game returned in early 2026, but the stadiums were empty. In an empty gallery every sound lands like a question — the bat's click, the clatter of the stumps, the umpire's single call. That was when I understood that silent cricket is also information-poor cricket; who said what, who did not — keeping those records now fell entirely on a few people outside the dressing room. There was one good thing about that empty stretch. I built a plain 'noise index' in my notebook — attendance, how much roar per innings, whether the away support travelled. The numbers are not exact, but they are enough to sense the life of a match. Because a scorecard never tells you how that match actually felt. Now to the real question of the ledger. Cricket is, in essence, a ledger. Every ball is an entry. Every run is an entry. An innings is a balance. That ledger was first kept by a scorer, in pen and paper; later by a computer, in a database. The question was never whether there would be a ledger. The question was who holds its key. That question is rising again, because cricket's data is now a digital asset. Broadcast rights, fan engagement, collectibles, fantasy play — everything rests on data. Whoever can say 'this ball was legal, that one was not' effectively controls a part of the game. This is the pull of blockchain-style technology. An immutable ledger that no one can unilaterally erase is an alluring idea for cricket. Boards have begun experimenting. Digital collectibles, fan tokens, tickets and memorabilia. Around 2026-22, Cricket Australia released NFT-based collectibles; in Europe football clubs moved into fan tokens, and cricket began walking that path too. From outside it looks as if the game is now fully digital, fully protected. But a trap hides here. Blockchain can make information immutable; it cannot make it true. What enters the ledger is decided by a human — the field scorer, the referee, the match official. Blockchain will not decide whether the ball was a wide; the umpire will. A sensor may measure how far the bat moved, but whether that is a shot or a miss is a human call. I have often seen two records of the same match differ. One app says Bangladesh made 245, another says 246, because one scorer logged a bye as a leg-bye and the other as a bye. Blockchain can immortalise that bye, but whether it is a bye or a leg-bye remains in human hands. This is where the fan archives are impossible to dismiss. In my Facebook group I have seen thousands of entries — who scored how many, who fell in which over, who got injured. Often the correct information arrives in the group before the official update. A fan sitting in the ground types it in, and that entry later matches the official record. It is no formal duty, but it works. There is another side to record-keeping that nobody counts — who provides the information, and who pays for it. Behind every scorecard is a fixer, a local journalist, a volunteer scorer. They often work without a byline. The news carries only the player's name, never the name of the person who gathered the data. Yet without that data the news would not exist. I have a rule — exactly thirty days after any labour or wage story, I file a follow-up. Why? Because everyone reads the story on day one and then forgets; but the victim's ledger keeps running that day too. Cricket's ledger is not only runs and wickets; it is also money. Another thing worth noticing — the over-load on young players. Football has minute trackers; cricket has balls and overs. How many overs a 19-year-old bowler bowls in a stretch, how many matches he plays — that count is usually kept nowhere. Yet it tells you who stays fit over the next three years and who breaks down. I added a simple young-bowler tracker to my weekly column, simply because nobody was keeping it. The ICC rankings are another kind of ledger. Each match result enters a formula and produces a number. The problem is that this number changes every week, and its explanation is not in the ordinary viewer's hands. So the same team sits third one week and fourth the next, and nobody can quite say why. Take net run rate. In a tournament group stage, who advances is often decided by a calculated number. One over of play can flip it. Who makes that number? A formula, written by humans. In rain-affected matches the target shifts by the Duckworth-Lewis-Stern method — again a human-made formula that fans have questioned for years. In other words, data is not neutral truth; it is a decision, with someone behind it. Now the opposite side. Everyone assumes more data means more truth. In cricket it is often the reverse. The more data grows, the more room for misreading grows. Take strike rate. In T20 a high strike rate means aggression, everyone knows that. But an opener who makes 36 off 40 at a strike rate of 90 and a finisher who makes 11 off 12 at a strike rate of 90 have identical numbers, yet utterly different roles. The scorecard shows them the same. And another fallacy — official means accurate. In my experience the biggest errors are often in official systems, precisely because they are the least challenged. Nobody questions them, because they are official. Yet a volunteer sitting in a scorer's chair for an hour may be writing with more care. The promise of blockchain and NFTs is also overstated here. A digital collectible does not grant immortality; it immortalises a pixel, not its market value. Cricket's real asset is not a token but the memory of a particular match — what a spectator felt sitting in the ground, what a father tells his son. That cannot be locked into a blockchain. Think of fantasy cricket too. Every tournament, millions pick teams, and that demand pushes data to be faster and more detailed. But that pressure does not improve the quality of data, only its speed. Speed and accuracy are not the same thing, and in cricket's ledger that difference is life and death. I have spent years in the ground watching fans argue over these formulas. Some call the formula cruel; some call it the only fair path. The real point is that the more complex the number, the fewer hands can interpret it. And where interpretation is centralised, so is the voice of the data. So the fan archive is not mere nostalgia; it is a kind of power-sharing. When a supporter writes the score down by hand, he is not only preserving memory — he is building an alternative ledger that runs alongside the authority's. And that is exactly where cricket's data and cricket's people touch. One moderator in my group kept a line-by-line note of every match for several seasons. No institution paid him, no recognition came. Yet today many turn to him for the details of an old match. This is the true form of ledger-keeping — unofficial, yet indispensable. When I first entered this beat, I thought data meant neutral numbers. Now I know every number has a decision behind it, and every decision has a person behind it. The match I write about today becomes history tomorrow — but who writes that history is being decided today, quietly. So the question is not who keeps more data — the question is who tells the data's story, and who gets written out of it. The table may freeze again, a server may crash, a live feed may drop, a single rule-change note may flip a whole season's arithmetic. But as long as one spectator sits in a ground writing the score by hand, cricket's ledger will never be zero. I now keep two columns in my notebook — an official score and a fan score. Year after year, the fan score wins most of the time. Next season, if the live feed drops again, I know where to look — outside Gate Five of the stadium, where a man stands holding a handwritten score.