Kumar Kushagra (GT): Third-Choice Keeper With No Data to Project
Kumar Kushagra does not make GT's optimal XII. His T20 data is effectively zero, with only 8 career balls faced for 3 runs. That sample provides no evaluable signal for any statistical model.
Why He Does Not Make the XI
GT's wicketkeeping duties go to Buttler, with Banton as backup. Kushagra sits behind both as the third-choice keeper. Without meaningful batting data, the model cannot project any value. His WAR/M is not calculable.
What We Know
Kushagra scored 3 runs at 38 SR across 8 balls split between PP, middle, and death phases. No statistical conclusions can be drawn from this sample. He could be an excellent batter whose tiny sample misrepresents his ability, or he could be a limited player. The data does not tell us either way.
His wicketkeeping ability is an asset that the model does not capture. Keeping quality matters for team performance, but our WAR framework evaluates batting and bowling only. Kushagra's value may be higher than his batting numbers suggest if his glovework is strong.
Development Path
Kushagra's path to the XI requires both Buttler and Banton to be unavailable simultaneously, which would be unusual. Even in that scenario, GT could ask another player to keep wicket in a pinch. His realistic role is emergency cover who benefits from training in an IPL environment.
What This Means for IPL 2026
Kushagra is a squad depth option who provides emergency wicketkeeping cover. He is unlikely to play in IPL 2026 barring extraordinary circumstances. His value to GT is as a long-term development prospect in the keeping department.