IPL 2017 Final vs RPS
Mumbai Indians win 2017 IPL Final by 1 run against RPS.
The Rising Pune Supergiant (RPS) faced the Mumbai Indians in the 2017 IPL Final at Hyderabad. This was RPS's last game in the IPL.
Quick Facts
- Winner
- Mumbai Indians
- Margin
- 1 run
- Venue
- Rajiv Gandhi International Stadium, Hyderabad
- Toss winner
- Rising Pune Supergiant (elected to field)
- Player of the match
- Krunal Pandya
Lore & Background
RPS had a psychological edge over Mumbai, having beaten them on all three meetings in the season. Rohit Sharma won the toss and decided to bat first. Jaydev Unadkat and Adam Zampa took key wickets as Mumbai crumbled to 79-7, but a late surge from Krunal Pandya meant Mumbai finished with a slightly below par score of 129–8. RPS looked comfortable after the powerplay but over-cautious batting cost them dearly. Ajinkya Rahane scored runs easily but captain Steve Smith struggled, and things took a turn when Rahane got out for 44. MS Dhoni arrived but was quickly removed for 10, and Pune were left requiring 11 runs from the last over with Smith and Manoj Tiwary at the crease. Tiwary hit a four on the first ball off Mitchell Johnson's bowling, and RPS looked to have the trophy in the bag. But Smith was run out on the second ball, and Tiwary was caught out on the third ball, leaving RPS requiring 7 runs from 3 balls. A single from Washington Sundar and a double from Daniel Christian meant RPS required 4 runs from the last ball. Unfortunately, RPS could only complete two runs before Sundar was run out. Thus, Mumbai Indians won by 1 run to get their 3rd IPL title.
Reader's Guide
The final over: first ball – Manoj Tiwary hit a four; second ball – Steve Smith was run out; third ball – Manoj Tiwary was caught out. The Player of the Match was Hardik Pandya.
Did You Know?
- The Rising Pune Supergiant's last game in the IPL was the 2017 final, which they lost to Mumbai Indians by 1 run.
- Hardik Pandya was the Player of the Match in the 2017 IPL Final.
Origins and Temporary Mandate
The Rising Pune Supergiant emerged as a unique, two-season entity within the Indian Premier League landscape, serving as a direct replacement for franchises suspended due to betting scandals. Owned by the RP-Sanjiv Goenka Group, the team was officially unveiled in Kolkata on January 18, 2016, with Raghu Iyer appointed as CEO. Alongside the Gujarat Lions, RPS filled the void left by Chennai Super Kings and Rajasthan Royals for the 2016 and 2017 tournaments. The franchise was deeply rooted in Pune, Maharashtra, utilizing the Maharashtra Cricket Association Stadium as its primary home ground, though severe drought conditions and subsequent legal interventions forced a temporary relocation of matches to Vishakhapatnam during their inaugural season. Despite initial struggles to establish dominance, the team successfully navigated its brief existence, culminating in a dramatic run to the 2017 final before being disbanded when the original franchises returned in 2018.
The 2016 Rollercoaster Campaign
RPS's debut season was characterized by extreme volatility and narrow escapes. They began spectacularly with a convincing nine-wicket victory over defending champions Mumbai Indians, only to suffer four consecutive defeats that threatened their standing. The team found brief redemption through strategic player inclusions like Ashok Dinda and Australian batsmen Usman Khawaja and George Bailey, securing crucial wins against Sunrisers Hyderabad and Delhi Daredevils. However, the season's most defining moment occurred in their final league match against Kings XI Punjab. After falling behind with only two balls remaining and needing 12 runs, Dhoni smashed two consecutive sixes to secure a victory that saved the team from the bottom of the table. Despite these highs, they finished seventh overall, winning just five of fourteen matches.
The Historic 2017 Run
The 2017 season marked RPS's zenith, driven by significant strategic shifts and high-profile acquisitions. The franchise rebranded to 'Rising Pune Supergiant' (singular) in March 2017 and appointed Steve Smith as captain alongside MS Dhoni. A record-breaking auction purchase of Ben Stokes for ₹14.5 Crore proved pivotal, complemented by the late addition of Imran Tahir, who became a match-winner with 18 wickets. After a shaky start mirroring their previous year, the team found rhythm, winning seven of eight crucial matches to qualify for the playoffs. They defeated Mumbai Indians in Qualifier 1 thanks to Washington Sundar's career-best bowling figures and a composed batting display. This momentum carried them into the final against Mumbai Indians at Hyderabad, where they held a psychological advantage having won all three prior league encounters.
Legacy and Franchise Evolution
The Rising Pune Supergiant concluded its IPL journey in heartbreaking fashion during the 2017 Final. Despite a solid start by Ajinkya Rahane, the collapse accelerated when captain Steve Smith struggled and MS Dhoni was dismissed quickly for just 10 runs. The team ultimately lost by a single run in their very last match, marking the end of their two-year tenure as the league returned to its original structure. However, the legacy of the franchise's ownership endured; the RP-Sanjiv Goenka Group later secured a permanent spot in the IPL ecosystem by acquiring the Lucknow Super Giants in February 2022. This new franchise now stands among the league's ten teams, continuing the owner's commitment to the sport long after RPS was disbanded.
Frequently Asked Questions
What was the final margin of victory in this match?
The game concluded with Mumbai Indians winning by just one run, thanks to a dramatic six hit on the very last ball.
Who was named Player of the Match for his all-round performance?
Krunal Pandya received the award after contributing crucially with both bat and ball during the high-pressure final.
Where did this historic encounter take place?
The match was held at the Rajiv Gandhi International Stadium in Hyderabad, which served as a neutral venue for the decider.
More in Iconic Matches & Finals
Elsewhere in Mumbai Indians
Spotted an error? Know more?
Reader corrections go straight into our review queue. Suggest an edit · How this site is sourced