Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: May 16, 2017, 09:07 PM (IST)
Edited: May 16, 2017, 09:07 PM (IST)
Rising Pune Supergiant (RPS) batsman Ajinkya Rahane registered 3,000 runs in Indian Premier League (IPL) in the ongoing Qualifier I match between his side and Mumbai Indians (MI) at Wankhede Stadium, Mumbai. Rahane has had a dismal run in the IPL 2017 but 3 of his 4 highest scores in this season has come against Mumbai Indian (MI), which includes this innings. He becomes the 11th player after Suresh Raina, Virat Kohli, Rohit Sharma, Gautam Gambhir, David Warner, Robin Uthappa, Chris Gayle, Shikhar Dhawan, AB de Villiers and MS Dhoni to get to the 3,000 IPL runs. Full Cricket Scorecard: Mumbai Indians vs Rising Pune Supergiant, IPL 2017, Qualifier 1 at Mumbai
Rahane brought up the feat in his 110th IPL match and his average is a touch short of 34. Rahane started playing for MI before moving to Rajasthan Royals, where he found a lot of success and slammed his maiden IPL hundred in 2012. Rahane is one of the highest paid players in the RPS set-up. Follow live blog of Qualifier I
Rahane reached the feat when he was on 44. He eventually scored 56, and finished today’s match with 3,012 runs. RPS had finished the league stage at No. 2 spot, notching up 9 wins from 14 games. The Steven Smith-led unit lost the toss in the crucial first Qualifier game and batted first. Having lost the first 2 wickets in the first 2 overs, Rahane and Manoj Tiwary brought normalcy to the score board. After 12 overs, RPS were 83 for 2 with Rahane registering his 25th IPL fifty — before he fell to Karn Sharma.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.