Kevin Pietersen undecided on playing in Lahore

Says will make a decision if Quetta reach PSL final


Nabil Tahir February 19, 2017
Photo courtesy: PCB

KARACHI: Former England Batsman Kevin Pietersen, star of the show for Quetta Gladiators in their clash with Lahore Qalandars, has said he will make a decision about whether to play in the Pakistan Super League (PSL) final in Lahore once his side qualifies for that title-deciding game.

“I haven’t yet decided whether to go or not; if Quetta reaches the final then I will decide on it,” said the right-handed batsman, who scored an unbeaten 88 to help his side chase down Lahore’s 200-run total. “Right now the team has momentum behind it and we will hopefully reach the final.”

The 36-year-old was happy he could turn around his PSL form, which had previously seen him score three runs in three innings. “I play my innings according to the need of the team," said Pietersen. "Today I was able to play some good shots so I kept on going.”

History repeats itself as Quetta chase 201 against Lahore


Lahore had been the first team to reach the 200-run mark in this year’s PSL but Pietersen believes sometimes chasing such totals is easier. “When you have 200 runs to chase it is easier than chasing 120 since you aren’t looking at the target but instead just keep on hitting.”

The controversial batsman added he was not worried about his poor form. “I was in the top 10 run-scorers during Australia’s Big Bash League so my recent lean run wasn’t bothering me,” he said. “In sports, you have more bad days than you have good days.”

Pietersen recently decided to drop out of the Indian Premier League, citing family reasons for doing so. “I have no plans to play cricket after this PSL ends since I have to give time to my family,” he said. “I have a young family and a daughter of one. I will think about what to do in the summer.”

COMMENTS (1)

Anon | 4 years ago | Reply Come on KP!!
Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ