U-19 Asia Cup: 240 Out of 250 — Auditing India's Selection Logic Behind Lakshya Raichandani's Aggregate

Lakshya Raichandani made 250 runs in three innings across the four-day series against Australia. Of those, 240 came in the first innings. The remaining two innings produced ten runs between them. Ninety-six per cent of a series aggregate sits inside a single knock. When I wrote that line into my notebook, questioning Raichandani's talent was pointless — the talent is established. The real question was what a selection table does with the distance between 240 and 10. The Under-19 Asia Cup runs from 4 to 14 November in Muscat, Oman, and India's fifteen-man squad is already named. The headline wrote itself: Virender Sehwag's son Aaryavir and Rahul Dravid's son Anvay both found a place. My desk asks the reverse question. India have picked two wicketkeepers for a tournament in which they can play seven matches at most. What exactly is the second keeper insuring? I began radio commentary from Hyderabad at nineteen, when scorebooks were filled by hand, and the first thing that trade taught me was that a big innings and a big total are two different objects. Forty years on, that lesson is still the foundation of this column.

Context first. India are in Group A alongside Nepal, Pakistan and the United Arab Emirates. Group B holds Bangladesh, Afghanistan, Malaysia and Sri Lanka. The top two from each group reach the semifinals. Raichandani captains, Yashvardhan Chauhan is his deputy. The fifteen are Raichandani, Aaryavir Sehwag, V.K. Vineet, Chauhan, Kushagra Ojha, Arjun Rajput, Manal Chauhan, Anvay Dravid (wicketkeeper), Rajat Baghel (wicketkeeper), V. Yashveer, Aaryan Savsani, Mohit Ulva, Kavya Patel, Shavin Vinod and Ishan Sud. The arithmetic is plain: seven batters, two keepers, six bowlers. India's pre-tournament form looks immaculate on one side of the ledger — Australia were whitewashed 2-0 in the four-day series in September–October and beaten 3-0 in the one-dayers. On the other side, the two-match four-day series against Sri Lanka was won 1-0 while the one-day series was lost 2-1. That second line weighs more with me than the first, and I will explain why.

Start with the number that generated this column. A 240 in four-day cricket means a batter went three or four hours without once having to re-examine his technique — he found a rhythm once and never lost it. Fifty-over cricket grants no such interval. Every ten overs brings a new-ball squeeze, a shifting required rate, a different method of scoring. Raichandani's 240 was an excellent innings, but it is not a forecast for a fifty-over tournament — in Muscat he will be playing a different game. Which is why the most bankable batting line in this squad belongs to the deputy, not the captain. Chauhan made 176 runs in two one-day innings against Australia, with a century in the second match — seventy-six in the first. Two innings, both worth more than fifty, one converted past three figures. The sample is small; the shape is right. The selection question should have been whose run curve survives the switch to fifty overs, and that answer points at Chauhan. The model did not predict the one-run final; it merely explained why we should have seen it coming. The work here is identical — not prophecy, but identifying the mechanism.

Now the part everyone is watching and almost nobody has audited. Aaryavir Sehwag made 28, 47 and 34 in the one-day series against Australia — three starts, all clustered near thirty, none converted. In age-group cricket that is the commonest and most dangerous pattern there is: the batter sees the ball well and cannot extend the innings. Three starts are proof of talent; they are not proof of selection merit — merit lives in the conversion ratio, and that ratio currently reads zero. Anvay Dravid's numbers are more interesting still. Two innings against Australia produced 38 and 9. Before that, in the final one-dayer of the Sri Lanka series, he made 87 off 67 balls. His one substantial performance therefore arrived in a series India lost 2-1, and in a match that no highlights package will preserve. I do not have ball-by-ball keeping data for Anvay, and without it I will not deliver a verdict on his selection. That is precisely the problem. We judge a wicketkeeper by the only number we publish about him — runs — and runs are the smallest part of his job. At the auction table, every bid is a confession about what the market cannot measure; here the market is not money but column inches, and it remembers the 87, not the 38.

Third, the part nobody counts. Two keepers in fifteen. If Anvay is first choice, Rajat Baghel spends the entire tournament on the bench unless there is an injury. India play three group games and, at most, a semifinal and a final — five or six matches. In that narrow window, a bench slot that cannot take the field is a slot that should have gone to a sixth seamer or a third spinner. The 7-2-6 split tells you the selectors counted cover rather than counting impact. And the fourth part — the win we are all treating as evidence. A 3-0 over Australia is not evidence in any model I would publish; three one-dayers are an anecdote with a scorecard attached. Australian Under-19 sides touring Indian conditions have historically underperformed, and calling that weakness a trend after three matches is the oldest habit of my profession. Take it from someone who has run the desk: I trust the dashboard, but I audit the story it tells.

Now the place where I attack my own argument. First weakness: Under-19 data is the least durable data in cricket. A sixteen-year-old bowler rebuilds his action in six months and every number goes stale. My model's error rate at this age will always be high, and I will not hide it. Second: it is entirely possible that I am describing a surname premium as a market distortion while the selection committee is watching far more cricket than my spreadsheet. That is plausible, and I accept it. Third, plainly: India will top Group A. I am with the consensus here, not against it. The difference is that the consensus attributes it to the 3-0 over Australia, whereas I attribute it to the bowling depth of Nepal, Pakistan and the UAE, which is unlikely to bowl India out twice in five matches. And the Pakistan fixture? I was born on the other side of that border, and I read it as a net run-rate variable rather than as poetry. It is an ICC-event scheduling fact, not an inherited romance.

So the real question before Muscat is whether this team is betting on one Raichandani innings or on Chauhan's repeatable shape. I am filing my stake with a date attached so it cannot be moved later. Before the final of this tournament, Chauhan will have scored more runs for India than Raichandani — a forecast built on fifty-over shape, not on a four-day 240. After 14 November I will enter this column in my annual scorecard exactly as hits and misses are entered. To everyone asking how Sehwag's son will bat, I have one question, and it belongs to the ball-by-ball sheet nobody currently holds: will we read balls faced before we read the surname next time?