Twenty Years of Silence: A Report from Ahmedabad's Nets, Where the Ball's Sound Speaks, Not the Scoreboard

Nine forty in the morning. Third net at the practice ground next to the Narendra Modi Stadium. A left-hand batsman, whose name does not matter at this moment, is not moving forward to the spinner. He is going back. Not feet first, bat first. I turned to page three hundred and fifty of my fourth diary and wrote — 'twelfth ball, fifth time back. Not forward.' This is not a big discovery. It is just a note, which I have been writing for forty years, and am still writing today. This stadium is not new to me. In February 2026, standing behind the Gujarat nets at this very practice ground, I watched Axar Patel's arm angle against left-handers. Four mornings. I wrote a cautious note that England's top order would not be able to score off the straight ball. Axar took eleven wickets, England made 112 and 81, and India won by ten wickets inside two days. At the time my desk wanted the 'pink-ball magic' angle. I refused. I filed on the length Axar had bowled in a Ranji semifinal three seasons earlier, on the same ground. The pink ball had not changed the game. The light had. And I had seen the light with my own eyes, not on an app's screenshot. This article does not begin like a match report, because there is no match today. This is a report from a training ground. I have been in Ahmedabad for the last eighteen days, and every morning from half past eight to one in the afternoon I am among these nets. I do not know whether what I am seeing is part of a series, a tournament, or a selection. I do not even know where the team practising here will play next month. When I was moved to the digital desk in 2026 and handed the Gujarat Lions beat, I filed a 600-word nets notebook from the Rajkot camp for forty-one consecutive days while the franchise slid to seventh with four wins from fourteen. Traffic was modest. But the team's video analyst screenshotted two of my seam-position notes, and the format outlived the franchise. Something similar is happening here. I am not watching the scoreboard. I am listening to the sound of the ball. This may sound strange, but in an empty stadium, where there is no applause, you can hear the bat and the ball separately. And that sound never lies. When a batsman drives and the ball comes off the middle, the sound is 'tak'. When it takes the edge, it is 'tuk'. When it misses, it is 'thap' on the pad, and if it goes into the wicketkeeper's gloves, it is 'phad'. In these four sounds lies the whole story of a batsman's innings, and that story is truer than any data dashboard, because it belongs to the moment when the batsman is making a decision. I have a rule, which I made in 2026 sitting at my digital desk: the two-source rule. Anything seen at training needs either the player's own words or a coach's confirmation. Never an agent's statement. This rule slowed my copy by a day and made it the most quoted on the beat. This morning, I watched a spinner working on his length. He was landing fourteen balls in a row in the same spot, while on the other side of the nets a fast bowler was changing the length of his run-up. I noted both. I asked no one anything, because I know that until I have two sources, this will remain an observation, not a conclusion. You have to understand one thing here. In the last few years, a whole industry of data has grown up in cricket. Every team has analysts, every broadcaster has graphics, every app has 'win probability'. And I am not saying all of this is useless. I am saying it is all incomplete until you have verified it on the ground, in the nets, and in the sound of an empty stadium. I have a ninety-sessions test. I measure every new tool — from DRS to the Impact Player rule, from tracking apps to data desks — by how many nets sessions it takes to earn my trust. I publish that timeline. The point is not technophobia. The point is that a method must survive eyewitness verification before it earns a sentence in my copy. In this Ahmedabad camp, I have noted something I had never recorded so clearly before. The rhythm of the nets. In the first hour of the morning, when the body is cold, bowlers work on their length — short run-up, slow pace, just form. In the second hour, when the sweat comes, there is speed. In the third hour, when fatigue sets in, the real technique emerges, because in a tired body only habits remain. I have seen that the batsman who can repeat the same footwork in the third hour that he showed in the first is the one who survives in a match. The rest, who look brilliant in the first hour and collapse in the third, are merely practice heroes. This is my personal experience, and I am drawing it from my diary, not from any model. Now the thing you probably will not find here. Around the world, and especially in Asia, a large part of cricket journalism now runs on auction and transfer rumours. Which team bought whom, whose purse is left with how much, which agent talked to whom. I am forbidden from covering all this, because it breaks the contract between me and the reader. I report what a document or a session shows, not what a bidder might do. If I write from here today that 'according to sources, this player may be bought by such-and-such team next season', I will make the mistake a beat keeper never makes. One thing I can say with certainty: whatever is happening in this camp is not a rehearsal for any selection or transfer. It is just cricket, and that is enough in itself. Here is a counter-intuitive point. When I sat on the sports desk of The Times of India in 2026, we had no data, no tracking, no Hawk-Eye, no precise use of the speed gun. But even then we understood the match, because we were at the ground, and our eyes and our diaries were our data. Today we have the speed of every ball, the angle of every shot, the wagon wheel of every batsman, yet I often meet journalists who do not spend even an hour in the nets. They build their stories from dashboards. And that is where the mistake happens, which I call 'dashboard-as-argument' — when you take a screenshot as fact, without explaining how the number was produced. My entire authority rests on having watched the thing myself. If I lose that, I become just an app that talks. My father taught me one thing when I first went out to report: 'Write what you have seen; check twice what you have heard; and never write what you have thought.' Forty years later, I would add: check on the nets what you have seen on the app. That is my ninety-sessions test. And in this Ahmedabad camp, I have not yet found the app to be entirely right. Some things it gets right, some not. But when I match what it says with what my eyes say, only then does a trustworthy sentence form. I remember that empty-stadium Ranji final of 2026, when Saurashtra beat Bengal on first-innings lead, with Jaydev Unadkat's sixty-seven-wicket season. It was the last major cricket played in India before the shutdown. Then eight months of silence. I did not write features in those eight months. I digitised my thirty-one years of two hundred and fourteen notebooks, indexed by ground, bowler and session. When domestic cricket resumed, I was the only reporter on the beat who could pull a 2026 Motera pitch note in under a minute. This is not a strength. It is just work. And it is this work that has brought me to this empty stadium today, where there is no applause, but there is the ball, the bat, and that morning sound that still brings a sixty-four-year-old man to the job. Now back to the nets. This morning I opened my first diary — from 2026, when I was new at The Times of India. I found a page on which I had written about a twenty-year-old fast bowler who would stop at one point in his run-up and then suddenly accelerate. That boy never played international cricket, but that habit — stopping, then bursting — I saw it three times that session. And I had thought, 'If he learns to control this, he will be dangerous.' He could not. But today, forty years later, when I watch a young fast bowler in this Ahmedabad net, I see the same tic. And I quietly write: 'Remember this. Not now, but three seasons later.' This is what I can give my reader — a date, a morning, a sound of the ball, and a note, which may never be published, but which will form the basis of my next article. I have a prediction ledger — every pre-match technical claim, dated and signed. Every March I read it again. That ledger has made me slower to call anything a 'breakthrough', and much harder to fool. By 2026, I would not describe a batting collapse until I had checked the ball-tracking and the pitch report myself. And this Ahmedabad camp, right now, is adding a new page to my next ledger. I do not know where this team will play next month. I do not know which series these players are preparing for. But I do know that at nine forty in the morning, in the third net, when the ball landed, there was a sound — and that sound was true. And that truth, one day, will become a headline. Perhaps soon, perhaps very late. But when it does, I will know that I heard it first, not on a screen, but in that morning air, where there was only the ball, the bat, and an old man's diary. The question is not what this team will do tomorrow. The question is: when it does, will you have someone who has seen it, who has already seen it from the nets?