Empty Data, Full Stadium: The Cricket Analysis Truth the Scorecard Won't Show

What you see on a cricket field is not always what is actually happening. In an Asia Cup match, I saw a batsman given out—DRS showed the ball hitting the pitch, but when I watched the replay on the big screen, the ball's track was different. This was not new to me. I have been covering cricket for 23 years, and every time data and naked eye diverge, I am reminded that the game we talk about is actually a system—and to understand the system, the scorecard alone is not enough. In recent years, the face of cricket analysis has changed. Asia Cup, IPL, bilateral series—everywhere, data rules. Analysts in the commentary box no longer just say 'it was a good ball'; they say 'this ball came at 142 kmph, and its seam movement was 2.3 degrees'. But there is a catch. This data is often incomplete. When I was sitting in a fan park in Chennai, I saw how 200 people were watching the same clip repeatedly—a catch that was probably dropped, but the umpire gave it out. The crowd was screaming, but no one had data. This is the real problem with cricket analysis: we read the scorecard, but we do not read the system behind it. The core of my argument is that every decision in cricket is made within a format, and if you remove the format, the data becomes meaningless. A bowler's economy of 8 in T20 means something else; 2.5 in Test means something else. When I saw a spinner concede 40 runs in 4 overs in an Asia Cup match, the commentator said 'he proved expensive'. But in the same match, another spinner gave 28 runs in 4 overs and took two wickets—so was the first bowler bad? No. The first bowler bowled in the 12th and 16th overs, when batsmen were set and the field was spread. The second bowled in the powerplay. Here, data must be seen not within the format but within the match situation. I have a live auction spreadsheet in which I calculate the price of every ball—but that price matters only when you know which over the ball was bowled in. I watched the Germany vs South Korea match in 2026. When Germany lost 0-2, I wrote that FIFA's group stage punishes big teams, while cricket's bilateral calendar protects them. I apply the same to cricket today. Whether it is India vs Pakistan in the Asia Cup or Mumbai vs Chennai in the IPL, the format of every tournament determines which player is how valuable. A batsman who strikes at 150 in T20 can become a burden in ODIs at a strike rate of 90—because there you need to score 300, not 200. In my spreadsheet, I keep each player's value in separate columns by format. When a franchise bought an all-rounder for Rs 14.5 crore, I calculated his value separately in T20, ODI and Test. The result was startling: in T20 he was a bargain, in ODI average, and in Test he could not make any team's playing XI. But no one asked this question. Because in cricket we look at price from only one angle—and that angle is T20. Now look at the moment when rain stopped play in an Asia Cup match. The target changed under Duckworth-Lewis-Stern (DLS), and a team that was scoring 180 in 20 overs now had to score 150 in 15 overs. The commentator said 'this is easy'. But I pulled out my spreadsheet and saw that scoring 150 in 15 overs on that pitch was as difficult as 180 in 20. Why? Because spinners were getting turn on that pitch, and in 15 overs you had 5 overs fewer—meaning it was difficult to fully use the spinners' quota of 4 overs. This is the detail the scorecard does not show. DLS is a format, and within that format you have to recalculate the price of every ball. After that match I tweeted: 'Rain did not stop the match, it changed the format.' That tweet got 2026 retweets, but no one asked who the new format benefits. One more thing needs to be added here. In cricket we often use the word 'star'. A young player scores 300 runs in the IPL, and the media starts calling him the next Sachin. But I have seen in my spreadsheet that 60% of batsmen who score 300 runs in the IPL have maintained an average below 30 in international cricket the following year. Why? Because IPL pitches are flat, and the quality of bowling is different too. When the same batsman plays in the Asia Cup, where spinners get turn and fast bowlers get reverse swing, his game changes. I am not saying IPL data is useless—I am saying IPL data is only for the IPL. When I watched the double Super Over match in IPL 2026, I wrote that 'the crowd noise is not real'—because the stadium was empty and crowd noise was being played on TV. That column was read by 600,000 people, and broadcasters called. But the real question was: if the crowd is fake, is the data we are seeing also fake? The answer is no, but it is incomplete. The graphics shown on TV are correct only for that format. When you use a T20 graphic to decide a Test, you are wrong. I admit there is a weakness in my argument. I cannot say data always tells the truth. There have been many moments in cricket when data was wrong. In the 2026 World Cup final, MS Dhoni scored 79, while his tournament average was below 30. Data said he was out of form, but he played his biggest innings on the biggest occasion. I will not call that innings a 'defeat of data'—I will call it a 'performance beyond data'. But that innings proved that data is just a tool, and the one using the tool must know when to put it away. In my spreadsheet there is a column called 'intangibles', where I assign scores to pressure, occasion and match situation. It is not perfect, but it is necessary. The second weakness is that I sometimes attach crowd sentiment to data. When I asked 200 people at a Chennai fan park which player they liked best, 80% named a batsman whose average in that series was 25. I gave that sentiment space in my column, but I cannot say that sentiment was right. Crowd sentiment is a data point, but it is not cricket data. I have used the word 'we' sparingly in my columns, because saying 'we' makes it seem like everyone thinks alike. When I started a Zoom watch-along in 2026, 200 people joined—but those 200 people did not represent all of India. They were just 200 people. I learned from that experience that before saying 'we', one should think about who 'we' are. Now a third weakness. I was born in Australia and work in India. For me, the Indian cricket boardroom is a room I can peek into from outside. But sometimes I use templates from other markets and try to fit them onto Indian cricket. For example, I once suggested that Indian players should play in foreign T20 leagues—but the Board of Control for Cricket in India (BCCI) policy is that active Indian players do not play in foreign leagues. I should have remembered that. This is the limit of my 'outsider's eye'. I can see the Indian cricket system from outside, but I cannot change it. And I should not try to change it—only understand it. So what is the right way? For me, the right way is to write the 'denominator' with every data point. When I say a bowler is expensive, I should also say which over he was bowling in. When I say a batsman is good, I should also say which pitch he was playing on. I have a live auction spreadsheet, and I carry it to every match. It has a column called 'source', where I write where the data came from—ICC website, broadcaster graphic, or my own observation. When I wrote about the Rs 14.5 crore deal in 2026, I had to issue a correction on retention rules. After that I hired a fact-checker. Now I check every number twice before writing any article. This is my 'correction scar', and I do not hide it. Look ahead. The next Asia Cup match is between India and Pakistan. Both teams have piles of data—one has a 200 kmph bowler, the other a batsman with a 150 strike rate. But the real question is: is this data right for that format? On Indian pitches spinners rule, and Pakistan's fast bowlers get reverse swing. If you look only at T20 data, you will think it is the era of batsmen. But in reality it will be a bowlers' contest. My prediction is that the score in this match will be below 300, and the team batting first will stop around 280. Why? Because Asia Cup pitches are a bit slow, and the fear of DLS is always there. If you ask me who will win, I will say the team with the better spinner. But I will also say that if rain comes, DLS mathematics will change everything. And that is the truth of cricket—data can prepare you, but the match is decided on the field. For me, cricket is not just a game, it is a system. And to understand the system, you have to understand its format. Until you know which format makes which player valuable, you will just drift with the crowd. I do not drift with the crowd—I mute the crowd noise and then listen. And when you mute, you hear what the scorecard does not tell you.