Rising Asia Cup 2026: India A and Pakistan A Drawn in the Same Group, Set to Meet in Doha on November 22

There is a page in my notebook from last year's Rising Asia Cup that is still folded at the corner. It is folded because it carries two lines that do not meet. One says Pakistan A beat Sri Lanka A by five runs in the second semi-final. The other says the final against Bangladesh A was tied at 125 and settled in a Super Over. Both can be true. I simply do not have the one scorecard that puts them on the same sheet, and until I do, I will not use either as a fact.

That incompleteness is the real context of this announcement. The Asian Cricket Council has released the schedule for the 2026 Rising Asia Cup — eight teams, two groups, eleven days, fifteen matches. The tournament opens on November 19 at the UDST Cricket Ground in Doha and closes on November 29 with the final at the West End Park International Cricket Stadium. Group B holds India A, Pakistan A, Nepal and the UAE. Group A holds Bangladesh A, Sri Lanka A, Afghanistan A and Hong Kong China. The top two from each group advance.

And then November 22 — India A against Pakistan A, the date everyone will frame as the tournament's face. India A begin on November 20 against Nepal and finish their group on November 24 against the UAE. Three matches in five days, with a single rest day in between. Jitesh Sharma captains India A; Vaibhav Sooryavanshi is in the squad. The conversation is already fixed on a match that has not been played, while the decisions that actually shape the group will be written in the two games around it.

I learned in the Uppal flat that leaving is a rhythm, not an exit. The same applies to a tournament schedule. Fifteen matches in eleven days, and roughly ten or eleven of them on the single square at West End Park. I have watched A-team and domestic cricket from the training-ground side for years now, and I watch training grounds the way others read sheet music. A square that hosts ten matches in eleven days changes character by the final week — spin finds turn, seamers start trusting cutters, and evening dew under lights takes the grip out of the second innings. Rain in Doha in late November is a low risk; dew is not written anywhere on the schedule, and it is the thing that quietly rewrites every captain's bowling plan before a semi-final.

Last year's record is a mirror with fog on it. Pakistan A are the defending champions, Bangladesh A were the losing finalists, Sri Lanka A lost a semi-final by five runs, India A went out in a Super Over. India A also beat the UAE by 148 runs, posted 297 for 4 in one innings, and in the same campaign were bowled out for 136 and lost a chase inside 13.2 overs. All four lines belong to one team. They do not tell you how strong India A are. They tell you India A's output is not stable.

The real variable in the race for the top two is not the result on November 22 — it is net run rate. That sounds inverted, but the arithmetic is simple. In a round-robin, one defeat does not remove you; you are removed when your three-match net run rate falls below the side you are fighting for the second slot. What carried India A to the semi-finals last year was a 148-run win over the UAE — a margin, not a performance. The same applies now: building a large gap against Nepal and the UAE matters as much as beating Pakistan A. This is precisely where young sides err. They conserve energy for the big fixture and settle for a 40-run win in the small one.

On group composition, one counter-intuitive point. On 2026 form, Group A is the deeper group — three of last year's four knockout sides sit there (Bangladesh A, Sri Lanka A and Afghanistan A), while Group B is top-heavy with two strong sides and two associates. The direct consequence is that both India A and Pakistan A have a materially easier paper route to the semi-finals than anyone in Group A. That is why November 22 matters less for the shape of Group B and more for the question of whom you meet in the knockout.

What stings most about India A's 2026 campaign is not a defeat but a variance signature. A side that made 297 for 4 was bowled out for 136 and lost that chase inside 13.2 overs. Then won by six wickets. Then had a semi-final tied and lost the Super Over. That is not a stable baseline; it is behaviour that swings with conditions and match state — a team that crosses 200 when the ground suits it and folds to 130 when it does not. At A-team level this matters because players are redefining their roles every single match.

Three games in five days is a genuine tactical constraint on a young pace attack, and it is invisible on the schedule. November 20, 22 and 24, with one day between each. No fast bowler can deliver four overs at full intensity three times in that spacing. It means the captain has to decide on November 20 whether his quickest bowler stays fresh for Pakistan A. And a second question follows immediately: if you rest your main seamers against Nepal and the game goes close, who absorbs the net run rate damage? This is exactly where a young team's coach and captain often pull in different directions.

Jitesh Sharma's appointment as captain is the single most informative signal about the nature of this event. Handing the armband to a capped wicketkeeper-batter confirms that the Rising Asia Cup is not an age-capped under-23 event but a de facto fringe-senior squad fixture. This is where players who are standing at the senior team's door but not inside it come to play. Read that way, the tournament is a leadership audition as much as a development exercise. The wicketkeeper-batter carries an extra load, because his hands take the most punishment — standing through three matches in five days, going down for every ball.

Vaibhav Sooryavanshi's name requires caution. His presence in the squad is a pipeline marker, not a performance data point. Being named on an India A sheet at his age tells you where the system is filing him; it says nothing about his technique, his spin-hitting or his tempo control. Anyone framing him as a finished product is in the same hurry that has always damaged A-team cricket.

Nepal replacing Oman in Group B is the least discussed and most consequential change in the schedule. Last year the group held two Gulf sides; this year it holds Nepal, whose senior side is a genuine T20I-standard associate. India A's November 20 opener is therefore a less forgiving warm-up than the calendar implies. The UAE, meanwhile, hold an advantage no scorecard records — climate and conditions are most familiar to them. All eight sides are at a neutral venue, but neutrality is not equally distributed.

Now to the reading error that looks most reasonable from outside. To an outside eye, November 22 is the centre of this tournament; from inside, it is its least decisive match. The cross-border weight of India–Pakistan is real, the two boards do not play bilateral cricket, and ACC events are the only structural meeting point — all true. But at A-team level this is a contest between two squads that turn over almost entirely each year. The team that made 297 for 4 has no connection to that score now. Extracting senior-level prestige from this fixture is the same mistake repeated every season.

The second outside assumption concerns Pakistan A's 'defending champions' tag. Last year's knockout stage produced two Super Overs — the semi-final and the final. When a title and an exit are both settled by a coin-flip-adjacent mechanism, 'defending champions' is a label to use carefully. It is as much evidence of fortune as of strength.

The third point troubles me most. 297 for 4 is a statistical outlier for a 20-over ACC fixture, and building a batting-depth story on it is dangerous. At 14.85 runs per over, the figure sits at the extreme edge of plausible T20 scoring. If last year's edition was in fact a 50-over event, the entire comparative frame collapses and every conclusion built on it is void. The 2026 format is not confirmed either. Until both are settled, I will hold last year's numbers as context, not proof.

The losing room taught me that silence can be a build-up. The way that semi-final stopped at a tie and slipped away in a Super Over has attached a story to India A that will reactivate the moment they reach another semi-final. The most valuable signal this time will not be a result; it will be how the team handles that old story when it gets there.

What I will be watching is written in the margins. Who bowls against Nepal on November 20 will reveal how much weight the team management places on November 22. Whether the squad sheet carries a second wicketkeeper will reveal whether Jitesh Sharma is a necessity or an option. And the largest signal will sit outside the tournament: this event falls immediately before the December auction and scouting cycle, which means a good week here adds far more to a player's price than his cricket justifies.

By the evening of November 22, Group B will already have taken its real shape. The crowd hears noise; I hear who is keeping time. The question is not who wins that night. The question is whether India A still have their fast bowlers by then, and whether they have banked the margin against Nepal and the UAE that will eventually carry them into the semi-final.