MI vs CSK Timeline: The Story of a Rivalry That Changed the IPL Forever

Rivalries aren’t born overnight; they gain that standing through many meetings, close results and leadership contests which split homes all over India.
Mumbai Indians against Chennai Super Kings did just that. It turned into the most-watched match in the IPL, as it wasn’t simply two teams, but two cultures, two schools of captaincy, and two ways of dealing with stress.
If you look for an MI versus CSK history, you’re really asking what made this contest the league’s main story, year after year?
This is that story, through the years which mattered, the finals which made reputations, and the small happenings that kept the conflict going, even if one team was rebuilding.

In Depth

2008–09: The First Sign

The IPL started in 2008, with all teams still working out what they wanted to be. Chennai seemed “ready” from the first week – a settled main group, a calm captain in MS Dhoni, and a Chepauk identity based on control.
Mumbai, on the other hand, were still making their personality. The early MI years had star players, but didn’t have the clear role definition they would later be known for.

Their very first IPL game set the pattern. Chennai made a very large score in Chennai, and Mumbai got close enough to make it a chase to recall. Even in that first season, CSK versus MI had a bigger-match feel than a normal league game.
By 2009, the conflict hadn’t fully become a trophy contest yet, but the difference was already clear: Chennai’s structure, against Mumbai’s search for balance. That difference is the base of every part which came after.

2010: The First Final

Every great rivalry needs a high-risk game that changes how people speak about it. For MI and CSK, that game was the 2010 IPL final.
Chennai made a strong total and kept it, defeating Mumbai to win the trophy. It mattered to both teams in different ways. For CSK, it proved Dhoni’s method: take on pressure, stay calm, win the big one. For MI, it made the need that would not go away: you don’t just want to beat your rival in the league, you want to beat them when it’s for the trophy.

This is a key point in any MI versus CSK history: 2010 is where the game stopped being “big” and started being “historical”.

2011–12: Teams Become Brands

In 2011, CSK won again, and the league began to understand that Chennai weren’t a one-season success. At the same time, Mumbai were moving to a clearer identity: finding better players, defining roles, building a bowling group which could finish games.

These seasons also made the emotional background that powers the rivalry to this day. CSK became the team which valued experience and temperament. MI became the team which treated team-building as a long project, piling up talent across roles.
When these two met, it felt like two philosophies arguing through cricket.

2013–15: Finals And Control

Mumbai reached the 2013 final against CSK and won it, and that win did more than give a trophy. It changed the mental game. Mumbai weren’t chasing Chennai’s level any more, they were setting their own.

A key reason that final stays in every MI versus CSK history is how it looked: Mumbai’s bowlers squeezing, Chennai’s batting fighting to stay alive, the pressure moving like a wave. Kieron Pollard’s effect with the bat gave MI a defendable score, and the bowling group did the rest.
From that point on, MI versus CSK became the league’s best contest of trophy-level teams, not just popular teams.

Rivalries stay alive because they keep making new issues. In 2014, games between these two leaned into the tactical side: matchups, pace-off bowling, and the kind of middle-overs plans which decide T20s before the last over even starts.

Chennai’s strength was still control through spin and fielding strength. Mumbai’s strength was building a pace-and-power image which could win on flatter grounds.
What made the rivalry richer was that conditions didn’t break it. Chepauk, Wankhede, Dubai, neutral places: MI versus CSK stayed competitive because both sides knew how to travel with their strengths.

By 2015, the rivalry had reached full volume. Mumbai were piling up large totals with rough powerplay scoring, and they had death-bowling plans which seemed rehearsed.

Chennai, even when behind, kept pulling matches back into the contest. That’s a CSK trait which appears in every time: you think they’re out, then the chase suddenly has a heartbeat.

The 2015 final brought them together again, and Mumbai won in strong style. Rohit Sharma’s leadership in championship games started to seem almost unfair – he looked relaxed, made choices quickly, and didn’t get flustered, even with a noisy crowd and a very important situation.
By this point in the Mumbai versus Chennai story, the record in finals began to favour Mumbai. Chennai had won the first one, in 2010, however MI had taken the biggest games in their rivalry, in 2013 and 2015.

2016–19: Pause, Return, One-Run Final

Some years changed the way the rivalry went. When CSK weren’t in the league for a time, the MI versus CSK games stopped, but the rivalry didn’t end. Fans still compared the two sides – Mumbai’s constantly improving team, against the memory of Chennai’s system.

Mumbai winning once more in 2017 made the rivalry more important, even though they didn’t meet in a final that year. It gave the impression that MI were creating something which could be in charge no matter the pitch or the time.
When CSK came back, the rivalry didn’t require an introduction. It started up as if a TV series had stopped halfway through and was now continuing.

Chennai’s return in 2018 is one of the most important parts of the whole MI versus CSK story. It wasn’t only a return, it was a warning: CSK’s system works well, even after time away.

MI and CSK played games that season which felt like important tests. Chennai’s skill at dealing with hard situations, particularly when chasing a score, came back as a main part of the story. Mumbai had plenty of skill, but CSK’s experience kept causing problems for MI’s plans.

This was also when games between individual players got new life. Rohit against Dhoni wasn’t only captain against captain, it was quick decision-making against calm decision-making. Mumbai liked to attack and quickly change the game. Chennai liked to keep the game close until the last five overs, then finish off well.

If you had to show someone one game to explain why this rivalry is special, it would be the 2019 final.

Mumbai set 149. Chennai chased it as a team which was used to being in finals. Shane Watson’s innings took the chase on, Mumbai’s bowlers found good moments, and the game went right to the last over.

The end was by one run. Just one.

That game did two things at the same time: it made certain Mumbai’s advantage in finals against CSK, and it made certain Chennai’s identity as the team which never stops trying, whatever the score says.

The 2019 final also made the emotional “reason” behind the rivalry deeper. You weren’t watching for a brilliant win, you were watching to see who would give in first. Neither did, until the last ball.

2020–21: Change And Captains

These years added a modern part: groups of players started to change more quickly, games between players were based more on data, and teams began to make more flexible teams.

Mumbai’s championship win in 2020 showed how good their modern system was: deep batting, intention in the powerplay, and a bowling group which could bowl difficult overs on flat pitches.

Chennai’s championship win in 2021 showed a different truth: even as groups of players are updated, the CSK system still works when jobs are clear. Dhoni’s leadership remained the main part, and CSK’s ability to pick the correct players for the correct jobs kept giving a good result.

When MI and CSK met in this time, the rivalry became less about “who has more famous players” and more about “who plays their jobs under pressure”.

2022–24: New Names, Same Weight

As groups of players changed, the rivalry stayed strong because the importance didn’t require a final every year. The game itself carried importance.

For Mumbai, the story began to focus on their next group: young batters, a search for regular bowling groups, and the work of rebuilding while remaining able to compete.

For Chennai, the story focused on continuing and the last parts of the MS Dhoni time, with new leaders coming forward around him. CSK’s 2023 season, ending in another title, added new shine to the rivalry’s “two great teams” label. A proper MI versus CSK history doesn’t view certain seasons as unimportant; they are important, as rivalries outlast team changes. Supporters still show up, as even if one team is trying to work out its best eleven players, the game is still a kind of test.

By 2024, MI against CSK was completely in the time of impact players, bold starts to innings, and scores that could rise by twenty-five runs in a couple of overs.

One of the most recent, important games was at Wankhede, where Chennai got over two hundred runs, and yet still had to seriously struggle to hold their lead. Mumbai’s attempt to get the runs included a very good knock from Rohit Sharma which reminded people why the rivalry goes back to its most important players.

Games like these add a new bit to the MI versus CSK history: the rivalry is not simply about the final matches and remembering the past. It is also about if the older, best players can still be in charge in the quicker modern T20 game.

What Makes This IPL Rivalry?

A history is only useful if it explains the reason why. MI versus CSK became the main rivalry of the IPL for five reasons.

A clear look at the numbers and patterns of the rivalry

Numbers And Patterns

A history needs some points of reference, so the story doesn’t go away from what is real.

Head-to-head (IPL only, to the end of the 2025 season): Mumbai has a small lead overall, with Chennai not far behind. The difference is small enough that two games could change the news headlines.

Finals: CSK won the first final game in 2010. MI won the next three finals against CSK in 2013, 2015, and 2019.

Players who got the most runs and took the most wickets: Rohit Sharma is near the top of the rivalry’s run list, while bowlers like Lasith Malinga and Dwayne Bravo have made the story of taking wickets across different times.