Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: May 25, 2018, 07:11 PM (IST)
Edited: May 25, 2018, 07:11 PM (IST)
Shikhar Dhawan completed 4,000 IPL runs in Qualifier 2 of Vivo IPL 2018, between Sunrisers Hyderabad (SRH) and Kolkata Knight Riders (KKR) at Eden Gardens, Kolkata. Dhawan became the seventh Indian and eighth overall player to the landmark. He has had a decent season so far scoring 437 runs in 14 matches at 39.72 and a strike rate of 139.17, including the Qualifier 1 wherein he was dismissed for a golden duck. The others to score 4,000 in IPL history are Virat Kohli, Suresh Raina, Rohit Sharma, Gautam Gambhir, Robin Uthappa, David Warner (the only overseas cricketer to do this) and MS Dhoni.
In this match, Dhawan got to the individual landmark with a trademark flick, off KKR pacer Prasidh Krishna, for the first six of the night. Will he get a big one tonight?
Dhawan started his IPL campaign playing for Delhi Daredevils, in 2008. He scored 340 in his first season and was the third-highest run-scorer in the team. He scored 569 runs in 15 matches with 5 fifties in 2012, his most productive season. In that season he was third in the list of highest run-scorers, behind Chris Gayle (733) and Gautam Gambhir (590).
If SRH win the match, they will again gear up to meet Chennai Super Kings (CSK) in the summit clash of IPL 11. CSK prevailed over SRH in Qualifier 1 to become the first finalist of the season.
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.