Raghu Sharma registers 0.00 WAR per match in our system. He has no UUID, no T20 ball count, and no xImpact score. The squad data shows a fragment: an SRae of 0.1 and a batting surplus of 0.4, but these appear to be artifacts rather than meaningful projections.

The Data Problem

Our pipeline found no T20 match records for Sharma in Cricsheet or ESPN sources. Without ball-by-ball data, we cannot compute phase splits, matchup profiles, or bowling contributions. The squad file lists him as a batter who cannot bowl, which contradicts the previous version of this article that referenced bowling stats. Those numbers were erroneous, generated from a data mapping issue, and have been removed.

To be direct: we do not know what kind of T20 player Raghu Sharma is. We do not know his strike rate against pace, his boundary percentage, or whether he bats in the powerplay or the middle overs. The data simply does not exist in our system.

Squad Context

Sharma is a domestic batter on Mumbai's bench. He does not carry an overseas slot, which gives him a marginal advantage over bench options like de Kock or Rutherford who would consume one of the 4 overseas spots. But marginal advantages only matter if you are close to selection, and Sharma is not.

Mumbai's Indian batting lineup features Rohit, SKY, Tilak, Hardik, and Dhir, all with established IPL track records. Sharma would need a significant opening to earn a game.

Projection

No meaningful projection is possible. The SRae and surplus figures in our dataset lack the underlying ball-by-ball evidence to be trusted. Sharma enters IPL 2026 as a squad depth player with no statistical case for selection. If he bats this season, we will build his profile from scratch.