Quaid Trophy: Ikramullah destroys Karachi Blues

Left-arm fast-bowler helps Abbottabad gain upper hand


Express December 01, 2011

Ikramullah Khan picked up eight for 51 on an action-packed second day as Abbottabad gained a 184-run lead against Karachi Blues in the ninth round of the Quaid-i-Azam Trophy.

According to information provided by the Pakistan Cricket Board, the left-armer destroyed the hosts’ batting line-up as Karachi were dismissed for 142 in the second-innings after Abbottabad made 216.

In reply, Abbottabad reached 110 for three with Mohammad Naeem contributing an unbeaten 42.

Abbas troubles Islamabad

Mohammad Abbas ran through the Islamabad batting line-up, taking seven for 58 to help Sialkot gain a 165-run lead on the second day. Abbas was supported by Mohammad Imran who took three for 34 as the hosts were bowled out for 140, conceding a 115-run lead, before Sialkot managed 55 for two by
day two.

Faisalabad set daunting total

In the context of the game, Faisalabad were set a daunting 274-run target after Rawalpindi were bowled out for the highest total of the match. Haseeb Azam hit 66, the only half-century of the game, to lead Rawalpindi to 198 in the second-inning after Faisalabad were bowled out for 104.

PIA on top against ZTBL

Kamran Sajid made a fine unbeaten 115 and Faisal Iqbal was on the verge of a well-made hundred as PIA piled on the runs against table toppers ZTBL.

PIA had reached a commanding 252 for two with Sajid and Iqbal remaining the unbeaten batsmen at stumps. Earlier, ZTBL had struggled to 178 in their first-innings in the face of some fine bowling by the PIA bowlers.

HBL dominate NBP

In another match, HBL fought well to reach 259 for six after NBP were sent packing for 243 in their first-innings. Elsewhere, SBP, facing a first-innings deficit of 160, had made five for no loss
against Wapda.

Published in The Express Tribune, December 2nd, 2011.

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