Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Feb 03, 2017, 01:52 PM (IST)
Edited: Feb 03, 2017, 01:59 PM (IST)
Kevin Pietersen, former England limited-overs batsman, has pulled out of the upcoming Indian Premier League (IPL) 2017. Pietersen, of late, has been playing domestic 20-over leagues across the globe, including Big Bash League (BBL), Ram Slam, among others. Pietersen last played in BBL 2016-17 for Melbourne Stars, who lost to Perth Scorchers in the semi-final clash by 7 wickets. Pietersen indicated travelling as the main reason for not featuring in the upcoming IPL auction. Already having spent his winter away from home, Pietersen does not want to miss out on family time in March and April.
Pietersen, in IPL 9, played for franchise Rising Pune Supergiants (RPS) under the leadership of MS Dhoni. Pietersen injured his calf muscle during RPS’ clash against Royal Challengers Bangalore and was hence ruled out of the tournament. He was released by the RPS franchise ahead of IPL 10 auction, which is to take place in February. Pietersen has played for Delhi Daredevils, Deccan Chargers and Royal Challengers Bangalore in the previous editions of the IPL. Pietersen has 1,001 runs to his name in IPL at an average of 38.50, with an impressive strike rate of 135 inclusive of a century. Kevin Pietersen fined for a taking jibe at umpire’s decision in BBL semi-final clash
FYI – I won’t be going into the IPL auction. My winter has been too busy with all my travel & I don’t want to spend April/May away too!
— KP (@KP24) February 3, 2017
TRENDING NOW
Earlier in the day, Pietersen was charged with a code-of-conduct breach in the recently-concluded BBL and was fined Aus$5,000 ($3,800) as stated by Cricket Australia (CA). Pietersen now has 48 hours to decide whether to appeal and have the matter heard by a CA code of conduct commissioner.
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.