
Skipper Imad Wasim scored an unbeaten ton to help Islamabad finish day one in strong position against Lahore Shalimar in their Quaid-e-Azam Trophy round four match at the Diamond Ground in the capital.
Islamabad opted to bat first after winning the toss, and justified the decision by finishing the day’s proceedings on 274 for seven in 85 overs. Wasim top-scored with a 106 runs while Afaq Raheem (38) and Moid Sheikh (34) chipped in with important knocks.
Mohammad Saeed and Waqar Ahmed got two wickets each.
In another match, medium pacer Naseer Akram claimed a five-for to help hosts Faisalabad bowl out Quetta cheaply at the Iqbal Stadium.
Asked to bat first, Quetta failed to show resistance and were bundled out for 167 in 65.5 overs as Naseer ran through their batting order while Adnan Munir claimed two scalps. Mohibullah scored 39 while Omar Qasim played a 37-run innings in an otherwise poor batting show.
In reply, Faisalabad had scored 31 for two in 10.3 overs.
Hyderabad make good comeback
Hyderabad made a good comeback at the end of day one by reducing Multan to 14 for two in their reply of 227 at the Multan Cricket Stadium.
Earlier, Hyderabad were all out for 227 in 70.4 overs with Haris Khan scoring 58 while Zafar Ali schipped in with an important 45. Aamir Yamin bagged four wickets while Mohammad Rameez and Haziq Habibullah got three scalps each.
Meanwhile in Group I, Israrullah played a 101-run knock to help Peshawar accumulate 317 for six in 74 overs against Abbottabad at the Arbab Niaz Stadium.
Sajjad Ahmed Jan (88) and Fawad Akbar (53) made important contributions in the innings. Kamran Ghulam took three wickets while Baber Khan registered two victims to his name.
Elsewhere, Jahangir Mirza’s 116 propelled Lahore Ravi to 278 for nine against Bahawalpur.
Published in The Express Tribune, November 17th, 2013.
Like Sports on Facebook, follow @ETribuneSports on Twitter to stay informed and join in the conversation.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ