Robin Minz has faced 15 T20 balls in our dataset. He scored 6 runs at a 40 SR. That number is meaningless in isolation. 15 balls is not a sample, it is a cameo.

The Keeper Dimension

Minz's value to Mumbai extends beyond his batting. He is a wicketkeeper-batter, which gives him a specific role in squad construction: backup to Ryan Rickelton behind the stumps. If Rickelton is rested, injured, or dropped to accommodate a different overseas combination, MI needs a keeper. Minz and Quinton de Kock are the options. De Kock takes an overseas slot. Minz does not.

That arithmetic is Minz's strongest selection argument. In any scenario where MI wants to play 4 overseas players and needs to swap out Rickelton, Minz becomes the only domestic keeping option.

What the Data Cannot Tell Us

We do not know Minz's strike rate against pace or spin. We do not know if he prefers the powerplay or the middle overs. We do not know his boundary percentage or dot ball tendency. 15 balls spread across what appears to be a single innings in the middle overs tells us nothing about his actual ability.

The squad data lists him as a batter (not a keeper) without bowling ability. His WAR per match is 0.00, and no xImpact score exists. The model cannot differentiate him from Mumbai's other zero-data bench options on statistical grounds.

Projection

None. Minz enters IPL 2026 as a keeper-in-waiting. His season likely consists of warm-up games and practice matches unless the Rickelton situation forces MI's hand. The 40 SR from 15 balls should be ignored entirely. If Minz plays a full match, that will be the first real data point we have.