Shivam Dube: Built for One Job in Chennai

Shivam Dube played two seasons for Royal Challengers Bengaluru and made 169 runs from thirteen innings at strike rates of 121.2 and 122.9. On that evidence he was a fringe domestic all-rounder who had been over-promoted, and Bengaluru let him go. He then played one season at Rajasthan Royals for 230 runs at 119.2, which did not change the picture much.

Since joining Chennai Super Kings in 2022 he has played 65 innings, made 1,730 runs at an average of 34.6, struck at better than 150 in three of five seasons, hit 115 sixes, and been picked in two India T20 World Cup squads, both of which won the tournament.

The player did not change nearly as much as those two records suggest. What changed was a specific decision by one franchise about where he would bat and what he would be asked to hit, and Dube's career is the cleanest demonstration in the competition of how much that decision is worth.

The two records side by side

Season	Team	Inns	Runs	Avg	SR	6s
2019	Royal Challengers Bengaluru	4	40	13.3	121.2	3
2020	Royal Challengers Bengaluru	9	129	18.4	122.9	9
2021	Rajasthan Royals	9	230	28.8	119.2	10
2022	Chennai Super Kings	11	289	28.9	156.2	16
2023	Chennai Super Kings	14	418	38.0	158.3	35
2024	Chennai Super Kings	14	396	36.0	162.3	28
2025	Chennai Super Kings	14	357	32.5	132.2	21
2026	Chennai Super Kings	12	270	38.6	158.8	15

The 2023 line is the one to sit with. Dube made 418 runs from 264 balls and hit 35 sixes — against only twelve fours. Three sixes for every four is a ratio almost nobody produces, and it is a direct statement about what he was being asked to do. He was not there to rotate strike and find gaps. He was there to hit the ball over the boundary, and the fours were largely accidents.

The job, stated precisely

Chennai's use of Dube was narrower and more deliberate than "middle-order hitter". He batted at three or four, entering during the middle overs, and his specific assignment was to attack slow bowling.

This is a real specialism and it is worth explaining why. In the IPL, overs seven to fifteen are dominated by spin — more so at Chepauk than anywhere, on surfaces that have historically rewarded it. Most Indian batters treat that phase as a period to accumulate against, because attacking a good spinner on a turning pitch carries a high risk of dismissal and a low expected return. A batter who can strike at better than 150 against spin in that phase does two things at once: he scores at a rate normally reserved for the powerplay or the death, and he forces the fielding captain to bowl seam in the middle overs instead, which is usually the worse option.

Dube is, by the published figures for the period since 2022, among the best in the world at exactly that. His strike rate against slow bowling across those seasons is the highest of any Indian batter with a comparable sample, and only a small number of overseas players — Heinrich Klaasen and Glenn Maxwell among them — rate higher. The precise figures vary with the innings cut-off chosen, which is why the claim is stated in that form rather than as a single number.

The mechanism is straightforward: he is a tall left-hander with a long reach and a very strong bottom hand, which lets him hit a good-length off-break from a spinner turning it away from him straight down the ground, and lets him get under anything slightly short. Neither shot requires the ball to be in a conventionally attackable spot, which is why field settings do not solve him.

Why Bengaluru and Rajasthan could not use him

The obvious question is why two other franchises had the same player and got nothing. Two answers, and both are structural.

First, batting position. At Bengaluru he was used mostly at five to seven — a finisher's slot, arriving with two or three overs left, facing seam bowlers at the death. That is the phase of the innings where Dube is least effective, because death bowling is wide yorkers and slower balls into the pitch, and his method depends on a length he can get to. Fifteen sixes in thirteen innings across 2019 and 2020 is not nothing; it just came with a strike rate of 122, because everything else was a dot.

Second, Bengaluru at the time had a middle order built around Virat Kohli and AB de Villiers occupying the very overs Dube needed. There was no version of that XI in which a young Indian all-rounder batted at four in the middle overs.

Chennai had the opposite arrangement: an order in which MS Dhoni finished, the middle overs were open, and the home ground was the most spin-dominated in the competition. It is close to the ideal set of conditions for the one thing Dube does exceptionally.

The all-rounder half, which quietly disappeared

Dube arrived as a genuine all-rounder. He bowled medium pace for Mumbai in domestic cricket, and his selection for India — including in the 2024 and 2026 T20 World Cup squads — was justified partly on the grounds that he offered a sixth bowling option alongside Hardik Pandya.

The bowling has largely gone. He bowled little for Chennai across the later seasons, and his IPL record carries no meaningful wicket tally. That matters for how his career should be read: he is not a bowling all-rounder who bats, and he is not really an all-rounder at all any more. He is a specialist middle-order batter who is occasionally listed as one, and the sides picking him are increasingly honest about that.

His international batting record reflects the same narrowing. In the 2024 T20 World Cup he made 133 runs at a strike rate under 115 — a poor return by his IPL standards, on Caribbean and American pitches that were slow and low and where the middle-over spin he feeds on was replaced by seamers hitting the surface hard. India won the tournament; Dube was a squad member who contributed rather than a decisive one.

The season that shows the dependency

2025 is the useful counter-season. Dube made 357 runs at 32.5 with a strike rate of 132.2 — his lowest at Chennai by 24 points — and 21 sixes from 270 balls. Nothing about his method or his position changed materially. What changed was that the pitches, at Chepauk and elsewhere, were reported as slower and lower than usual, and Chennai had a poor season overall.

That is the honest limit on the argument. Dube's value is unusually condition-dependent even by the standards of a specialist. Give him middle overs, spin and a surface with some pace in it and he is close to the most destructive Indian batter in the competition. Take away any one of the three and he is a batter averaging 32 at a strike rate in the low 130s, which is useful and not special. He recovered in 2026 — 270 runs at 38.6, striking at 158.8 — which suggests 2025 was conditions rather than decline.

What the career actually argues

The claim Dube's record supports is not about him being underrated or overrated. It is about how badly the standard way of assessing a T20 cricketer works.

His first three seasons produced 399 runs at 121 across three franchises, and any reasonable read of that evidence in 2021 was that he was not an IPL-standard batter. That read was wrong, and it was wrong not because the numbers were misleading but because they were measuring him doing a job he could not do. The same batter, given a different phase of the innings and a different type of bowling to attack, produced five seasons averaging around 35 at a strike rate near 150 and two World Cup squads.

Almost every squad list in franchise cricket contains a player in that position — good at something specific, being used for something else, and generating figures that look like a verdict. Dube's record is the argument for looking at what a batter is actually being asked to do before concluding anything from his average, and the reason it is a strong argument is that Chennai made the same discovery about the same player that two other franchises had already declined to make.

Sources and method

IPL season and career figures are taken from official competition records and cross-checked against this site's own match dataset. The T20 World Cup squad selections and Dube's 2024 tournament returns follow BCCI and ICC sources and official scorecards. Claims about his scoring rate against spin are stated in comparative rather than absolute terms because the published figures shift with the minimum-innings threshold applied; no such figure has been computed here. The description of batting positions by season is drawn from published scorecards rather than ball-by-ball data.