Rising Asia Cup 2026: India A vs Pakistan A in Doha on 22 November, and the Group B Arithmetic No Scorecard Records

297 runs, four wickets, twenty overs. 14.85 an over. That number sits at the very top of the spreadsheet in which I keep the record of ACC 'A'-team matches — India A posted exactly that against the United Arab Emirates last year and won by 148 runs. In the same campaign, days later, India A were bowled out for 136 and Pakistan A finished the chase in 13.2 overs. One team, one tournament, two numbers that refuse to recognise each other.

The Asian Cricket Council has now released the 2026 schedule: India A and Pakistan A are in the same group and meet in Doha on 22 November. I have the PDF open at two in the morning because the headlines have grabbed the date and dropped the rest of the document. The dropped part is the actual story this time.

Eight teams, two groups, eleven days, fifteen matches. Group A holds Sri Lanka A, Bangladesh A, Afghanistan A and Hong Kong China; Group B holds India A, Pakistan A, Nepal and the UAE. The tournament opens on 19 November at the UDST Cricket Ground, but the load falls on West End Park International Cricket Stadium — roughly ten or eleven matches on that one square, the final included. The final is on 29 November. Top two from each group reach the semi-finals.

India A's sequence reads: Nepal on 20 November, Pakistan A on 22 November, the third group game on 24 November. One rest day before the marquee fixture and one after. Last year Group B contained Oman; this year it contains Nepal. On paper that swap looks small. On grass it does not.

The 22 November fixture is not an elimination match for either side — and that is the least anticipated fact about it. In a top-two format the real stake sits on net run rate. Last year India A's campaign was effectively rescued by that 148-run margin; at 40 runs they would have been outside the semi-final race. The Nepal opener on 20 November is therefore not a decorative curtain-raiser but the first instalment of the arithmetic. Margin, not merely victory.

Four results from last year define this side: a 148-run win, an eight-wicket defeat inside 13.2 overs of the chase, a six-wicket win, and a tie. That is not a stable baseline; it is a variance signature — a team whose output moves with conditions and match state. In knockout cricket that temperament turns dangerous, and the 2026 semi-final is the proof of it.

Here I have to enter something awkward from my own desk. The available record describes Pakistan A as having won the title by beating Sri Lanka A by five runs in the second semi-final, while the next portion of the same record says the final against Bangladesh A finished tied at 125 and was settled in a Super Over. Both cannot be true at once. When a tournament's results do not reconcile with each other, the "defending champion" label handed out on their basis deserves caution. This is not carelessness on my part; it is the condition of a record nobody has verified.

The same record carries another marker. 297 for 4 in twenty overs sits at the extreme edge of plausible scoring for any ACC event. Every 2026 data point refers to twenty-over innings, so that edition is read here as a T20 event — but the 2026 format is not stated in the schedule. Until it is, every 2026 benchmark has to be carried as conditional.

Now the ground. Rain risk in Doha in late November is low, but evening fixtures run under lights and dew degrades a finger-spinner's grip in the second innings. Ten or eleven matches on one square across eleven days will leave the surface worn and spin-friendlier in the closing stages. The second week of this tournament will not be the same cricket as the first, and the schedule does not say so.

Three matches in five days, with a single rest day on either side, is a genuine constraint for a young fast-bowling attack. Rotation becomes compulsory, and rotation means your best new-ball pair may not be on the park on 22 November. The freshness question stays incomplete anyway, because Pakistan A's opening fixture date is not recorded in the available schedule.

On group depth an inverted conclusion emerges. Three of last year's four knockout participants sit in Group A — Bangladesh A, Sri Lanka A and Afghanistan A. Group B is top-heavy: two strong sides and two associates. The group containing the India-Pakistan fixture is the shallower one, which means both big teams have an easier structural route to the semi-finals. Nepal's inclusion trims that comfort slightly, because Nepal's senior side is a genuine T20I-standard associate, a harder opponent than Oman.

What I have on players is not performance data but a selection signal. Jitesh Sharma captained India A last year; a capped wicketkeeper-batter appearing here confirms this is not an age-capped U-23 event but the ground of fringe senior squads, and that the captaincy is a leadership audition too. Vaibhav Sooryavanshi's presence in the 2026 squad is a pipeline marker, not a data point — no batting figures are supplied, so any judgement on technique would be unsupported.

And that is the most honest thing about this entire file: there is not one player-level batting or bowling figure in the material available. This is schedule news, not performance analysis. A reporter who turns it into a form story is calling his inference data.

Now the thing the date-headline will not carry. India and Pakistan do not play bilateral cricket; ACC events are the only structural meeting point. The weight of 22 November is therefore as real as any scoreboard — dismissing it would be dismissing data. But watching that weight, one has to record as well that the least consequential match of this tournament is probably the one being sold hardest. In a top-two format, the side that loses on 22 November does not go home. The schedule is built so that a 29 November rematch stays alive — and that is a decision made by a calendar, not by cricket.

Third, and nobody will file it. The real audit of this tournament is not who lifts the trophy but how many of the eight boards send a full squad and how many send a courtesy XI. That number is not available on any fixture list.

Twelve years ago I sat on a similar desk and spent thirty-one nights on somebody else's tournament while the cricket I had actually watched died in the queue. That experience left one habit — read the document first, feel afterwards. This schedule demands the same order.

So what is there to watch in Doha on 22 November? Not who wins. Watch by how many runs India A beat Nepal on 20 November, because in the table that forms on the evening of 24 November, the 22 November result will be one line and that margin will be the whole column. The number that will explain this tournament again is not 297 for 4. It is India A's net run rate on the morning of 24 November.

And when that match is over, when the cameras move and the commentators pick up their next assignment, eleven days of wear will still be sitting on that one square. I write the pause after the roar, where the athlete becomes a person again — and here the pause is dated 30 November. On that day eight boards will face one clean question: who comes back to this calendar next time, and whose team stays on paper.