U19 Asia Cup: Raichandani Captain, Chouhan Vice-Captain, Sehwag and Dravid in Squad — and a Different Story in the Numbers

I opened my scorebook and the line from the release came back again. India has named a 15-member squad for the Under-19 Asia Cup. The first two names most people will read are Aaryavir Sehwag and Anvay Dravid. That is a natural thing to do. But in the performance numbers released with the squad, the biggest figure belongs to somebody else. Lakshya Raichandani, named captain, made 250 runs across three innings of the four-day series against Australia. Of those 250, 240 came in a single innings. The other two innings add up to ten runs.

That number is not a verdict on ability. It is a distribution. And any argument about captaincy, form or selection that does not break the distribution open stays incomplete. In the junior scorecards I have kept in my own book over the years, the same shape returns again and again: one large innings becomes the face of an entire series, and the empty space behind it goes unseen.

The Under-19 Asia Cup will be played in Muscat, Oman, from 4 to 14 November. The tournament is in the one-day format, and the preparation structure has followed it — four-day matches and 50-over series both. India are in Group A, alongside Nepal, Pakistan and the United Arab Emirates. Group B contains Bangladesh, Afghanistan, Malaysia and Sri Lanka. The top two from each group reach the semi-finals.

India play three matches in the group stage. That number carries a limit with it. No batter can get more than three innings before a semi-final. Calling someone 'in form' or 'out of form' on three innings is possible, but the claim leaves the reach of verification. That is why every average in this report is printed next to the innings count and the individual scores, so a reader can see where the average came from.

The 15-member squad is: Lakshya Raichandani (captain), Aaryavir Sehwag, V.K. Vineet, Yashvardhan Chouhan (vice-captain), Kushagra Ojha, Arjun Rajput, Manal Chauhan, Anvay Dravid (wicketkeeper), Rajat Baghel (wicketkeeper), V. Yashveer, Aryan Savsani, Mohit Ulva, Kavya Patel, Shavin Vinod and Ishan Sud.

Two wicketkeepers in one squad is a structural signal. The team management does not want the keeping load resting on a single person, which is a practical precaution in junior cricket where workloads shift without warning.

The preparation record is mixed, and that is the most useful thing about it. In September and October, India's youth side beat Australia 2-0 in the four-day series and 3-0 in the one-day series. Before that, they won a two-match four-day series against Sri Lanka 1-0 but lost the one-day series 2-1. So in the same preparation cycle, the team was unbeaten in one format and beaten in another. Anyone writing the sentence about 'excellent form' will leave that second half out.

Now to the ledger this team has actually been picked on.

The captain's ledger: 240 out of 250 is concentration, not consistency. Raichandani's three innings in the four-day series read 240, with ten runs across the remaining two. The average works out to 83.33, which looks excellent. But an average is a statistic that erases the shape of the distribution. Had his three innings been 90, 85 and 75, the total would still be 250, the average still 83.33, and the team would know it gets roughly the same thing every innings. 240 and ten means one extraordinary day and two empty ones. As a captain that is a risk, because the captain is the person a three-match group stage needs something from every game.

Let me raise the objection myself: three innings are three innings. Any batter in any series can produce three innings like that. The 240 also means he can take a game away in a single innings, and in junior cricket that is the most expensive skill there is, because the opposition has no experience of stopping him. The question is not whether he is good. The question is how his 83.33 should be read. My answer: not through the average, but through the innings-by-innings list. And that list says that the next time he stalls between 40 and 50 across two innings, it will not be a new decline. It will be his existing distribution, now visible.

The same standard applies to the vice-captain: two innings, 176 runs, average 88, one century. Yashvardhan Chouhan was India's most successful batter in the one-day series against Australia, with the hundred coming in the second match. Subtract the century from 176 and the other innings is 76 or less. Both his innings were productive; neither was empty. That shape is different from Raichandani's.

But the standard stays the same. Two innings, both good, is still a sample of fewer than three. If I treat the captain's three-innings average with suspicion, I have to treat the vice-captain's two-innings average with the same suspicion. The most common error in my own notebook is this: a number that supports the argument makes the sample look large, and a number that cuts against it makes the sample look small. Only one yardstick applied to both makes a comparison.

Two surnames, two different windows — and the story changes when the window moves. Aaryavir Sehwag made 28, 47 and 34 in the one-day series against Australia. Total 109, average 36.33, highest 47. Not a single fifty in three innings. That is not failure — 36 is a fine average at junior level — but it does raise the question of conversion. All three of his scores sit between twenty and fifty. That means he reads the bowlers, gets a start, and then stops. Getting a start is common in junior cricket. Taking it past fifty is rare.

Now look at Anvay Dravid. Two innings against Australia produced 38 and 9 — total 47, average 23.5. In that window he sits behind Aaryavir. Shift the window back slightly. In the last match of the one-day series against Sri Lanka he made 87 off 67 balls, a strike rate of 129.85. His last three one-day innings now read 87, 38, 9 — total 134, average 44.67.

What changed there was not the batter. It was the window. Six months ago, in a report on a domestic junior tournament, I watched the same thing happen: two players were being compared using one player's last three innings against the other's last two, and the conclusion had been decided before the counting began. Entry and exit dates belong in any data comparison, otherwise the comparison is already biased.

Anvay's value as a keeper goes beyond the gloves. 87 off 67 is the middle-order shape that matters most in 50-over cricket, because it forces the bowling to change in the last ten overs. Pair that with a second wicketkeeper in Rajat Baghel and the structure suggests the team sees Anvay as a batter who keeps, not merely a keeper. That is not printed on the list. It falls out of the shape of it.

The group stage is three matches long, and that is this team's largest unknown. Three games against Nepal, Pakistan and the United Arab Emirates. Three innings before a semi-final. Any batter's 'form' can turn twice in that span without the turn being real; it would only be noise. That is why I have not used the word form for any player in this report. Until the word is defined, it is an unfalsifiable claim carrying a paragraph it has not earned.

A small pattern kept returning, so I stopped calling it noise. Almost every number released with this 15-man list is a batting number. No bowler's overs, economy or wicket count appears in the public release. That page is blank in my book. When you name a squad of 15 and half of them are bowlers, half the squad's accounting is publicly unavailable. That imbalance has to be corrected before any meaningful evaluation can begin.

What is not in this dataset has to be written down too. How the Muscat surfaces behave, the November heat and humidity, the day-night difference, field settings, the captain's bowling rotation, injury status — none of it is in the numbers available. The figures built against Australia belong to one opponent in one time window. Applying them to three matches in Muscat is the easiest and most common mistake in my trade: treating one metric as universal. No comparison should be made without the format, the phase and the denominator, and here all three change.

Now the part where I have to disagree with my own argument.

The 3-0 against Australia is not form. It is one series against one opponent inside one preparation window. At the other end of that same window sits a one-day series lost 2-1 to Sri Lanka. Both facts belong to the same team, inside the same selection process. An analysis that picks up only the first fact is not analysis. It is a choice.

The second thing I doubt most is this: most of the discussion around this announcement will be spent on two surnames. That is understandable, because the story pulls readers. But if you want the most useful thing about this team, it is who bats in which phase in the middle order and who carries the bowling load. In cricket, possession and control are different things: scoring runs is possession, keeping wickets in hand is control. Junior teams routinely mistake possession for control, because in a three-match group stage a fast start looks like a win. The real question in Muscat will be how many wickets India have left after 20 overs. That number will describe the team's maturity. The powerplay score will not.

Third, I will not call Aaryavir's 28, 47 and 34 an average. It is a distribution in which every innings stops in the same place. If he stalls at 47 against Pakistan, that will not be a dip in performance; it will be his pattern. If he goes past 80, that will not be form either; it will be a change in skill. The difference matters, because the selection committee will have to decide on exactly that difference next time.

The notebook recorded the scene; the data recorded the shift. The scene is a 15-man squad containing the sons of two former greats, a captain who made 240 in an innings and a vice-captain who made a century in a one-day series. The shift is that the entire public record of this group runs to three to five innings, and half of it — the bowling — is missing. This is not a bad team. It is an under-documented one.

So watch for this. The Pakistan match in Group A is this team's first genuine test, because it is the only fixture where the opposition is a level above the preparation series. I will be watching how Raichandani bats in the first ten overs: a fast start means he is in his 240 mode, a measured start means he is more useful to the team. I will be watching whether Aaryavir goes past 47. And I will be watching whether the board releases the same detailed ledger for its bowlers that it released for its batters — because until it does, any opinion on half this team remains an estimate, however confidently it is written.