UP's Squad of 18: 24 Wickets Out, 53 Runs In — The Real Selection Failure Is at No. 5

There are 18 names on the list. The one missing took 24 wickets in the league. The one present made 53 runs in seven matches, highest score 25. After Uttar Pradesh named its Syed Mushtaq Ali Trophy squad, the argument collapsed onto that single pair — Abhinandan Singh out, Arnav Baliyan in. The thread started in the afternoon and ran past 1 a.m., and the real story in the replies was not that the selectors ignored the league. The real story was that the selectors did not ignore the league — they rewarded it selectively, and in that ordering they swapped a fast bowler for a middle-order batter whose public numbers support nothing. What looked like a hot take was actually a paper trail. I opened a spreadsheet and counted how much weight league numbers actually carry in a selection room.

First, the ground this argument stands on. The Syed Mushtaq Ali Trophy is India's premier domestic T20 competition — 38 teams, starting in Mumbai on 14 November. Wankhede's pitch is traditionally quick, the new ball offers seam movement, and dew in evening games makes middle-overs spin cheaper than it looks. Uttar Pradesh has history here: the 2026-16 final was played at Wankhede, where UP beat Baroda by 38 runs for their maiden title. Praveen Kumar was in that winning XI. He now heads the senior men's selection panel — the man who won a title on this ground is now picking the team for it.

Second, the context that matters: the UPT20 League was sold as the state's talent pipeline, with an implicit promise that league runs and wickets would convert into state caps. This cycle has another hole, and it is not a selection error: Rinku Singh is unavailable. He is at the ACC Men's Asia Cup Rising Stars in Qatar, which begins on 19 November. Rinku would have been the first name on this sheet, and his absence is the fuel under the whole debate.

Now the audit of the claim that started the row. The charge is that league performances counted for nothing. Count them and the opposite appears. Karan Sharma, the leading run-scorer of UPT20 League 2026 with 361, is in the squad and has been made captain. Zeeshan Ansari, the leading wicket-taker with 25, is in the squad. Sameer Rizvi, Swastik Chikara, Divyansh Joshi, Abhishek Goswami and Prashant Veer — all prominent league run-scorers — are in the 18. Seven of the league's eight headline performers were selected. This is arithmetic, and the arithmetic says this is not a case of ignoring the league, it is a case of distributing league numbers by role.

Questioning Karan Sharma's captaincy is the easiest thing to do and the least useful. His record is not a one-season spike: 606 runs in 2026, 519 in 2026, 361 in 2026 — three straight seasons among the league's top run-getters. Sustained scoring at domestic T20 level is rare, because bowlers arrive each season having read you and he still finds runs. With Rinku absent, this was the only logical captaincy call.

The real fracture is not in the bowling, it is in the surplus of bowling. Bhuvneshwar Kumar brings death-overs experience — yorkers, slower balls, the habit of closing an over under pressure. Mohsin Khan, Shivam Mavi, Yash Dayal and Kartik Tyagi together form pace depth that few domestic T20 sides can match. In spin, Zeeshan Ansari is a wicket-taking option with 25 scalps. That is six serious options for four slots. On a seam-friendly Mumbai pitch the marginal value of a seventh fast bowler is close to zero — which is the only honest defence of leaving Abhinandan out, and it is a role argument, not a merit argument.

But the moment that logic is applied to the batting, it breaks. With Rinku gone there is no proven finisher in the middle order. Karan Sharma is the pillar with 361; behind him are names like Sameer Rizvi and Swastik Chikara who can score quickly in T20 but not consistently. The No. 5-6 responsibility lands on a batter who made 53 runs in seven innings — about 7.5 per innings, best of 25. Evening games will bring dew, chasing will bring middle-overs spin, and UP has no batter with a domestic T20 record at No. 5. UP have six options in pace bowling and not one proven option at No. 5. Dropping 24 wickets is a luxury; picking a 53-run batter is not a necessity — and that is the inconsistency.

Here I have to argue against myself. Seven innings is not a sample; 53 runs might mean he was pushed down the order in small chases, or that he bowls too, which no report mentions. Abhinandan's 24 wickets do not prove a good economy rate or that the wickets came against top-order batters — in domestic T20, tail-end wickets also add up to 24. The selectors have watched the nets; I have watched scorecards. The unnamed panel member who said, on condition of anonymity, that UPCA will not produce a winning team without a transparent system is evidence of internal unease, not statistical proof of a wrong pick. Treating replies as data is the mistake every argument repeats. I am forming this view from Manchester off scorecards; what Praveen Kumar sees in the selection room is not in my spreadsheet, and assuming that three seasons of 606-519-361 read as small to someone else would be rash.

One thing does stay clear, and it is transparency. UPCA secretary Prem Manohar Gupta has said the picks were made on merit and that the chosen side is capable of winning the title — a standard defence that does not answer the one specific question of why Abhinandan was left out. A league sold as a talent pipeline selected its 25-wicket bowler and dropped its 24-wicket bowler. Had that distinction been written into the selection criteria, this argument would not exist. Uttar Pradesh has won this tournament before on structure, not on a single name; the 2026-16 title came from set-piece discipline and bowling control.

I will leave this on a testable prediction, because that is the only test numbers respect. UP's first two matches after 14 November will be at Wankhede; if their bowling concedes under nine an over in overs 17-20 across both, Abhinandan's omission goes into the file and the argument dies quietly. But if UP bat first and lose their fifth wicket before the 12th over with fewer than 85 on the board, the same argument returns within 48 hours — and then the question will not be about Abhinandan, it will be about the slot nobody wanted to fill. My bet: within a fortnight UPCA will have to put its selection criteria in writing, or this thread restarts at 1 a.m. next season. And I know I will be in it, spreadsheet open.