Musheer Khan sits outside the model's optimal XII. The model has no WAR per match data for him in the current dataset, which means he cannot be projected with the same framework used for the rest of the squad. He is listed as a batter with no bowling capability.

What the Model Sees

Khan's uuid (d621b427) is tracked in the system, but the critical fields (warPerMatch, battingWarPerMatch, bowlingWarPerMatch, t20Balls, regressedWarPerMatch) are all absent. Without these inputs, the model cannot generate a projection, a position fit, or a phase split analysis.

The old article data shows domestic T20 numbers: 1107 career runs at 148 SR across 67 matches. A middle-overs matchup split showed 163 SR vs pace (40 balls) but 100 SR vs spin (63 balls). A death-overs SR of 134 across 65 balls sits below the league average.

These numbers come from outside the IPL dataset and carry lower confidence. The pace vs spin split in the middle overs is the most interesting signal: a 63 point gap favoring pace.

Why He Misses the XII

Without WAR data, the model cannot justify selecting Khan over any of the twelve players who have quantified projections. PBKS' batting order is seven deep with established performers. Khan would need to displace Nehal Wadhera or Shashank Singh to earn a spot, and without IPL data, that case is impossible to make statistically.

What This Means for IPL 2026

Khan is a talent bet. His domestic pedigree and strong pace-hitting numbers suggest he could contribute if given opportunities. The middle-overs spin vulnerability (100 SR) is a red flag for a #5 or #6 batter who would face heavy spin diets. If PBKS give him matches early in the tournament, the data will accumulate quickly and the model can generate a proper projection. Until then, he remains outside the quantitative framework.