Zulqarnain rues Twenty20 snub

Lahore, Karachi, Multan overlook wicket-keeper for domestic event.


Express August 27, 2011

LAHORE:


Zulqarnain Haider, a star in the making for Pakistan 12 months ago, cannot even find a place in any regional team now.


Overlooked by the Lahore region for both their teams for the season-opening domestic Twenty20 event that takes place next week, Haider went looking for a place in some other region but Karachi and Multan, too, gave him a cold shoulder.

Lahore region opted to go with the Akmal brothers as their wicket-keepers while Multan, too, preferred to stick to their first-choice Gulraiz.

“It is disappointing to not be considered in either of the Lahore teams because this is my home region and if they don’t select me, who will,” complained Haider.

He had alleged on his Facebook page that the Akmal brothers were behind his ouster but the Lahore region president Khawaja Nadeem said that they have better and performing players to fill the void.

“Haider was out of cricket for the last year and in Twenty20, we require cricketers who are performing so we went for better performers,” he said.





Published in The Express Tribune, August 28th, 2011.

COMMENTS (5)

Ibrahim | 12 years ago | Reply

@Amer: @syed: Are you guys CRAZZZYY! He made the right decision to leave that the last game and go to England! He later resurfaced in the UK and said he fled since he had received death threats from unidentified people seeking to draw him into match-fixing. He tried to seek protection in the UK and placed an application for asylum that hinged on the nature of the information he was able to divulge, as the extraordinary nature of his case appeared to fall outside the usual conditions required of a person seeking refugee status.

RizwanTKhan | 12 years ago | Reply

We don't even want to see his face. And if he ever comes on field, i suggest we welcome him with pelted stones.

VIEW MORE COMMENTS
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