logo

MI vs CSK Timeline: How IPL’s Fiercest Rivalry Became a Cricket Classic

March 10, 2026
MI vs CSK Timeline

Some rivalries are based on where teams are from – this one was built on championships, how players handled stress, and the sort of leadership which can alter the course of a match in just four balls.

The MI versus CSK history isn’t only a list of games, it’s a record of the IPL coming to enjoy the pressure: Dhoni arranging plans, Rohit remaining collected, Chepauk getting louder, and Wankhede responding in kind.

From the last-over finish of 2008 to finals worked out by the smallest of margins, Mumbai Indians against Chennai Super Kings has repeatedly come back to the same thing – when the two play, the result is rarely certain.

How then did this become the IPL’s most important contest, and why does it still appear as though the whole season changes when blue plays yellow?

In Detail

2008: A Rivalry Begins

With a Six-Run Victory

The first part of the story was written in Chepauk on April 23rd, 2008, and it arrived complete: CSK made 208, MI almost got there, and the end had the sort of early-IPL mess which felt like street cricket, but with stadium lights.

That night was important because it immediately set the standard – large scores, large personalities, and the sense that both sides had the depth of team to go on rebuilding each year.

2009–2010: The Beginning Turns

into a Championship Story

By 2010, it wasn’t a “good game” any more, but a championship issue. CSK and MI met in the final at DY Patil, and CSK won by 22 runs after scoring 168.

That win gave Chennai a brand: take on pressure, then stop the other side scoring with fielding, slower deliveries, and Dhoni’s calm. For Mumbai, it created a need that kept returning in later years: they weren’t far away, but “not far away” doesn’t win you the championship.

2011–2012: When Styles Met

Supporters Chose Sides

These seasons didn’t require a final to feel important. CSK appeared to be a system, a side which knew what each player was to do: attack in the powerplay, control the middle overs, experience in the final overs. MI seemed a source of talent with a violent pace-and-power identity.

It was also when the rivalry got its usual pattern:

CSKtrying to manage the pace using spin and player matching.
MIattempting to make early openings, then squeeze with pace at the end.

The crowd culture became stronger too. Yellow made Chepauk feel like a festival. Blue made Wankhede feel like a Test match, loud and impatient, always expecting a return.

2013: The First Mumbai Victory

in a Final

The 2013 final at Eden Gardens was the first time the MI vs CSK history truly became a contest for the championship. Mumbai put up 148 and still won by 23 runs, as the pitch was slower, and MI’s bowlers carried out their plans.

Kieron Pollard’s effect was typical of MI: one burst, one change in how things were going, then control. CSK’s chase fell apart early, and Dhoni’s determined half-century came too late to alter what was happening.

That win did two things:

1It put Mumbai on the same level as Chennai in terms of championships.
2It began the “finals story” which still affects every meeting.

2014: A Year of Close Losses

and Player-Matching Battles

If 2013 was about a final, 2014 felt like a game of chess. The teams were very involved in player matching by that point. Mumbai’s pace attack, Chennai’s spin and changes, and both sides treating the middle overs as a negotiation.

Even when they weren’t playing in knockouts, the games began to feel like looking ahead: who bowls to who, who gives in first, which batter can hit a “safe” six for fourteen.

2015: Mumbai’s Highest Power

in their Second Victory in a Final

The 2015 final was the most forceful finals performance in this rivalry: MI scored 202, then held CSK to 161, winning by 41 runs. It was Mumbai at their most powerful: attack by the top order, power in the middle order, then accuracy in the final overs.

Rohit Sharma’s 50 from 26 in that final wasn’t only fast, it was tactical. He attacked the bowlers Chennai usually used to regain control, forcing CSK into defensive fields earlier than they would have wished.

This part of the story showed a truth: when MI’s batting works, CSK’s control method is put under stress, as there’s no “quiet” phase to squeeze.

2016–2017: Lack of Play Made

the Contest Feel Even Larger

The rivalry didn’t disappear, it paused. With CSK away for two seasons, Mumbai continued to build their dynasty, and the league missed that one contest which always felt like a test.

By the time CSK came back, the rivalry had become myth. Supporters didn’t only want the game back, they wanted the feeling back.

2018: CSK Return

Immediate Reminder

CSK’s return season was the ideal rivalry restart: experienced core, clear roles, and the sense that Dhoni didn’t need youth to outwit youth.

Even when MI had the better players on paper, CSK kept dragging games into the phase they like most: overs 7–15, where fields tighten and batters become impatient. The rivalry’s tactical identity came back strongly.

2019: The One-Run Final

Which Gave the Word “Classic” Meaning

If someone asks why this contest is loved, tell them to watch the 2019 final. Mumbai made 149. Chennai got to 148. One run. One decision. One act under the greatest pressure.

That game wasn’t a hitting contest. It was stress. Bumrah’s control, Malinga’s nerve, Watson’s wounded fight, Dhoni’s chase management, and an end which still seems unreal as it was worked out by a single ball in a single over. This is also where the contest moved away from being about ‘which team is better’ and turned into ‘which team deals with the pressure better’.

2020–2022: Years of Change

But Still the Same Battle

These years were different – more changes to the team, more players coming and going, and the leadership around the main players kept shifting. Still, the rivalry felt as strong as ever as both teams, even in poorer seasons, seemed to have a natural ability to perform.

For Mumbai, it was about getting the batting tempo right, and having a solid top order. For Chennai, it was about mixing experience with newer, more energetic players – especially with scoring rates in the league generally getting higher.

Even when one side was in a rebuilding phase, the game itself didn’t feel like a rebuilding phase game.

2023: Two Games

Two Different Results

In 2023 the rivalry showed how many sides it had. At Wankhede on April 8th, CSK chased down 157 to win by seven wickets, taking control of the chase in a calm and assured way.

Later in the season, at Chepauk, CSK beat Mumbai again in a match where the bowling plans and how they were put into practice were key. This showed something which often happens: CSK’s skill in turning ‘good Mumbai totals’ into ‘totals Mumbai are likely to be chased down’ by winning the middle overs.

2024: Rohit’s Century

Pathirana’s Response

The 2024 game at Wankhede produced a statistic that seemed unreal: Rohit Sharma scored 105 not out, but CSK still won by 20 runs after successfully defending 206.

That match was important in the Mumbai versus Chennai story, because it showed what IPL pressure is like in the modern game. A batsman can play a truly great innings and still lose if the other team controls the final overs. Matheesha Pathirana taking four wickets changed everything, and CSK’s defence felt like a very clever, late-night plan.

It also showed the modern side to this rivalry: along with well-known players, newer specialists are now the ones who decide the outcome.

Why This Rivalry Continues

to Be the IPL’s Highlight

The rivalry endures because it’s never been only about the players. It’s been about skills in high-pressure situations which can be relied on.

1) Captains who deal with unpredictability

Dhoni’s impact on this match-up is in the small things: a change in the field, a change of bowler, a calm single to keep a well-set batsman on strike. Rohit’s impact is in his emotional control: keeping the team’s shape even when the game seems to be going badly.

2) Specialist roles that are effective under pressure

Mumbai’s eras of death bowling with Malinga, then Bumrah, created endings that felt like traps. Chennai’s finishing ability – whether through Dhoni, Jadeja, or the next generation – created chases that lasted longer than they should.

3) The character of the venues really matters

Chepauk isn’t just ‘home advantage’, it’s a place where tactics are important. Wankhede isn’t just ‘good for batting’, it rewards strong play in the powerplay and clean hitting. This rivalry keeps changing in character because the venues demand different answers.

The Unofficial “Timeline Within

the Timeline”: Finals and Near-Finals

The rivalry’s best moments are, basically, a fight over a trophy cabinet:

2010 FinalCSK win by 22 runs.
2013 FinalMumbai win by 23 runs.
2015 FinalMumbai win by 41 runs.
2019 FinalMumbai win by 1 run.

This is why every league-stage Mumbai versus Chennai match has the energy of a knock-out game. Fans don’t watch it for ‘two points’. They watch it to see ‘who looks more ready for the play-offs right now’.

The Tactical Pattern Fans

Have Come to Expect

Over the years, fans have learned to watch this game in stages.

PowerplayMumbai try to score quickly, Chennai try to get through with as little damage as possible, and keep wickets for later. If Mumbai score 55 or more without losing more than one wicket, it changes the whole innings.
Middle oversChennai try to slow the scoring with clever player match-ups and field settings which tempt batsmen into risky shots. Mumbai try to get one batsman set and make the bowlers bowl the ball in the wrong place.
Death oversBoth teams want their best bowlers on the field. Mumbai’s best sides finish with yorkers and balls bowled at a hard length. Chennai’s best sides mix slower balls, balls bowled wide of the stumps, and a level of fielding effort which makes taking two runs feel almost impossible.

This is why the Mumbai versus Chennai story doesn’t feel repetitive. The players change, the pattern stays, and the pressure stays.

Key Points

1The Mumbai versus Chennai story began with a six-run CSK win in April 2008, and it’s been close enough to feel personal almost every season.
2They’ve met in four IPL finals (2010, 2013, 2015, 2019), with Mumbai winning three and Chennai winning one – including the one-run 2019 finish which still defines the rivalry.
3Recent games keep adding fuel: CSK beat Mumbai at Wankhede in 2024 even though Rohit scored 105*, while Mumbai’s 2025 chase of 176 in 15.4 overs showed what they’re capable of when the top order performs.
4The character of the venue shapes the result: Chepauk tends to reward control and player match-ups, Wankhede rewards strong play in the powerplay and clean hitting.
5The rivalry remains outstanding because it’s built on skills in repeatable pressure situations, not only on famous players.

Final Thoughts

This rivalry became a classic because it keeps producing the one thing IPL fans want: a match where both teams look like champions, even while one of them loses.

The Mumbai versus Chennai story is really the IPL’s story, too. Each era adds a new hero, a new finish, and a new reason why the next meeting feels like it has extra importance.

When the next season brings them together again, watch the powerplay, watch the player match-ups in the middle overs, and watch who stays calmer at the end. That’s where this rivalry always exists.

Author

  • Ahmed

    Ahmed Raja is a sports content writer with seven years experience of creating match-ups and evergreen content for sports news and betting sites. His specialty is cricket and football, turning complicated games into readable, practical breakdowns. He writes previews, team news, betting guides, and odds explanations and puts accuracy above all else. Won't resort to making stuff up, and uses boringly dry language to stop people from getting overly excited about gambling.

Posted in: IPLMatch Insights