Lahore Blues capture maiden win courtesy Iqbal's heroics

Bowler's match haul of 10 wickets pivotal in team's triumph

Our Correspondent October 05, 2017

KARACHI: A 10-wicket haul by Bilawal Iqbal helped Lahore Blues register their first victory of Quaid-e-Azam as they defeated NBP by an innings and four runs in their second round fixture at KRL Stadium in Rawalpindi.

Forced to follow-on, NBP resumed their second innings on 64-4 still trailing by 141 runs before they lost their entire line-up for 201 as Iqbal added six more wickets to his first innings tally of four wickets to win his side the game.

In another match at Abbotabad Cricket Stadium, SSGC registered their second victory by defeating Peshawar by 337 runs.

Chasing a mammoth total of 441 runs, Peshawar were restricted on 103 as Amir Yamin took four wickets and Muhammad Irfan Junior claimed two scalps.

In the other two Pool A matches, SNGPL resumed their first innings on 265-8 and were able to add only eight runs before losing all their wickets against Islamabad.

At the end of play, Islamabad were batting on 208-4 with a lead of 250 runs under their belt and the pairing of Faizan Riaz (62) and Sarmad Bhatti (43) on the crease.

Elsewhere, in the match between Wapda and Faisalabad, the former resumed their second innings on 140-5 and were able to reach 339, setting a target of 312 runs for the latter.

The highlight of the day was Kamran Akmal's 139 off 229 balls.

At the end of play, Faisalabad were batting on 83-5, needing 229 more runs to win.

In Pool B matches, PTV registered their first victory by defeating Karachi Whites by five wickets.

Elsewhere, FATA resumed their second innings on 52-1 before losing all their wickets with 166 runs on the board as KRL’s Yasir Ali took five wickets for 41 and Noman Ali took three for 16.

At the end of play, KRL — in pursuit of their 166-run target — were 72-1, still needing 94 more to win.



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