Sarfraz admits to feeling ‘insecure’ during Waqar’s tenure

Wicketkeeper-batsman says he abstained from speaking about issues to avoid getting dropped


Sports Desk January 25, 2017
Sarfraz says he abstained from speaking about issues to avoid getting dropped. PHOTO: AFP

Pakistan wicketkeeper-batsman Sarfraz Ahmed said on Tuesday that he abstained from speaking about problems he was facing during the tenure of previous head coach Waqar Younis because he was afraid of being dropped from the playing eleven.

Talking to a local TV channel, Pakistan’s T20I captain revealed that it was true he had requested the chief selector not to rest him for the tour of Zimbabwe because he felt insecure regarding his position in the team.

“I was a bit insecure because I had been dropped from previous T20I matches before the Zimbabwe tour and after performing well, I was concerned what would happen if my replacement performed well,” he said.

Yasir out, Irfan in as Pakistan announce squad for Australia ODIs

Responding to a question about the events of the 2015 World Cup in New Zealand and Australia where Waqar refused to play him in the first four matches, Sarfraz remained evasive in his replies and played down the issue.

“I felt scared to say too much,” he said. “It could lead to me being dropped. I feared being dropped from the team because I have seen it happen to some other players.”

Sarfraz Ahmed to return home following mother's illness

Sarfraz returned to Pakistan prior to the start of ODI series with Australia due to his mother’s ill health. In his absence, Mohammad Rizwan has been serving as the regular glovesman for the visitors Down Under.

COMMENTS (1)

Syed | 7 years ago | Reply Waqar has ruined his reputation by picking a biased view and making players insecure Sarfaraz, Afridi and others which will come out soon inpublic. He was not good for Pak team at all I hope he does not get a chance again as coach
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