Uttar Pradesh's Squad Selection: The 25-Wicket Arithmetic and the Missing Explanation

The Khulna screen flickered, and a byline started breathing. It was half past eleven on my balcony, the same clip looping for the fourth time — Zeeshan Ansari's 25th wicket, then Abhinandan Singh's 24th. Both from the UPT20 League, both under the same floodlights. The gap is one wicket. The arithmetic that built Uttar Pradesh's eighteen-man squad, though, was never a one-wicket sum. It was an explanation nobody supplied.

On November 10, 2026, the Uttar Pradesh Cricket Association named its squad for the Syed Mushtaq Ali Trophy, which begins on November 14 in Mumbai. Karan Sharma captains. Rinku Singh is absent, and that absence is not a selector's verdict: he is playing the ACC Men's Asia Cup Rising Stars in Qatar. A calendar collision, quietly reshaping the batting balance.

The questions arrived immediately. Several heavy UPT20 run-scorers and wicket-takers missed out. UPCA secretary Prem Manohar Gupta answered plainly: the selectors have picked a good side, one capable of winning the competition. Praveen Kumar heads the senior men's selection panel that finalised it.

Alongside that defence sits a sentence from an unnamed selection panel member: “Unless we have a transparent system in the UPCA, we aren't going to have a winning team.” The sentence is serious, and it is the most uncomfortable part of this story. The source is unnamed. No document, no panel minute, no corroboration.

My working habit is simple. In 2026 I built an empty-stadium archive from a bedroom in Khulna, sixty phone calls deep, one silent roar at a time. That is where I learned what a press release never says — a kit man's sigh says it instead. An unnamed quote is therefore valuable to me and suspect to me in the same breath.

I watch UPT20 from Khulna in the least glamorous way possible: clips, buffering streams, screenshots of scorecards. There is an advantage to watching Indian domestic T20 from this distance. No franchise hype, so the eye sticks to outcomes rather than launches. Twelve years of watching matches have taught me that a league's run chart and a team's role chart are rarely the same document.

T20 construction rests on four compartments. A powerplay batter who can weaponise the fielding restrictions. A middle-order batter who can hold scoring momentum. A finisher for overs 16 to 20. And in bowling, a death specialist plus a spinner who can control the middle. Fill those compartments or the names on paper stay on paper.

Karan Sharma's selection invites no argument. He made 606 runs in UPT20 2026, 519 in 2026 and 361 in 2026 — three seasons near the top of the same competition. Three seasons of repetition is stronger evidence than one season of explosion, because it suggests he scored after bowlers had already worked him out.

One sum is still missing. What is his strike rate? In how many innings did the 361 come? At which venues, in which phases? The 2026 number is lower than 2026 and 2026, yet without innings counts it cannot be called a slump. Fewer matches, fewer runs.

His leadership load matters too. When runs and captaincy sit in the same dressing-room chair, the arithmetic is easier. If his strike rate stalls in the first two games, the argument lands on his name rather than on the selectors' table.

The selectors did not ignore the league, a fact that gets flattened by the noise. Sameer Rizvi, Swastik Chikara, Divyansh Joshi, Abhishek Goswami and Prashant Veer are all in the eighteen. The decision was not selection versus exclusion. It was who was picked for which job.

Still, one comparison has to go on the table. Zeeshan Ansari, 25 wickets, selected. Abhinandan Singh, 24 wickets, omitted. A one-wicket margin, deciding a career fortnight.

Wickets do not describe a role in T20. Death bowlers take wickets, powerplay bowlers create pressure, middle-over bowlers are judged on economy. Which overs he bowled, against whom, at what economy, average and strike rate — none of it is public. Where the pillars of the explanation are missing, nobody can prove the decision was biased; nobody can prove it was sound either.

Transparency deserves specifics. Three disclosures would change the picture: the preference order, the role assigned to each pick, and written feedback to those left out. That does not change the squad. It tells the players outside which door opens inward.

Then there is Arnav Baliyan: seven matches, 53 runs, a highest score of 25, 7.57 runs per match. Beside Karan's 361 it is a small number, and small numbers raise the question. If his pick was role-based, one line would have settled it. No line came.

The gap between announcement and action opens right there. Saying “we reward league performance” while picking a 53-run batter and dropping a 24-wicket bowler does not hold together. A development league like UPT20 runs on a single guarantee: play well and the door opens.

The bowling picture is cleaner. Bhuvneshwar Kumar, Mohsin Khan, Shivam Mavi, Yash Dayal and Kartik Tyagi give genuine pace depth. Depth on paper and workload in reality are different currencies. Six weeks on the Al Ain team bus in 2026 taught me that a fast bowler's fitness lives on the physio table and the workload spreadsheet, not in the press conference.

Zeeshan is the documented spin option; who sits behind him is unclear. Rinku's absence leaves the biggest hole of all — the batting from overs 16 to 20. Replacing him is not swapping a name, it is manufacturing a finishing role.

In 2026-16, Uttar Pradesh won this competition with spread-out batting and disciplined bowling. Ten years on, the formula holds even as the personnel changed. History is not collateral for this squad, but it fixes the expectation — and expectation amplifies every missing explanation.

The outside reading is simple: talent dropped, or favouritism at work. Both camps argue about outcomes. Neither argues about process.

Mine is different. The crisis is not in the quality of the picks; it is in the quality of the explanation. Gupta defended the outcome, which is his job. Nobody said what weight league runs, domestic record, fitness and role each carry. A correct decision without an explanation eventually sounds like a weak one.

The second thread is subtler. The unnamed panel member's line may itself belong to an internal balance of power — who is influential, whose view was heard less, who wants the chair next cycle. I work on team access, so I draw the boundary early: access and evaluation do not sit at the same table.

Three scenarios are worth carrying. Worst case, unexplained calls repeat, player confidence erodes and panel friction spills out. Base case, the team plays, the argument hangs on results. Best case, UPCA publishes criteria and the team makes the question irrelevant.

A reader in Khulna messaged last night: “If 24 wickets isn't enough, how many is?” Fair question, unanswered. I cannot answer it either. One uncomfortable figure stands: four days before the tournament, the selection criteria remain unpublished.

My notebook has the watchlist for November 14 in Mumbai. Karan's powerplay strike rate. Zeeshan's middle-over economy. Who bats in overs 17 to 20 without Rinku. How many overs Bhuvneshwar bowls and how early he is pulled. And whether UPCA explains the rule that converts league performance into state selection.

I still refresh scorecards at 4 a.m. Matches end at night; the questions stay awake till dawn. Uttar Pradesh may well win this tournament and bury the argument under the table. The question will still be there, only later to be answered.