TODAY’S PAPER | October 28, 2026 | EPAPER

MIT Solutions fight back in PT final

Abuzar’s fifty puts them in good position against SBP on day-2


Sports Desk October 28, 2026 1 min read
Photo: AFP

MIT Solutions put themselves in a good position thanks to Abuzar Tariq’s solid 85 against State Bank of Pakistan (SBP)  on the second day of  their President’s Trophy Grade-1 match at the Bagh-e-Jinnah Ground on Wednesday.

MIT Solutions, who were dismissed for just 112 in their first innings responded strongly in their second innings as they reached 263-7 in 64 overs at stumps, for a lead of 203 with three wickets in hand. They had conceded a 60-run lead in the first innings.

Swat-born Abuzar anchored the recovery with a patient 148-ball innings, striking four fours and four sixes in a knock that lasted four hours and 37 minutes.

Salman Khan made 28, while Atiq-ur-Rehman chipped in with 23 as MIT Solutions steadied their innings. Abuzar then built the backbone of the total, helping his side recover from 61-3 at one stage.

Aitizaz Habib Khan contributed 32 off 33 balls before retiring hurt, while Test cricketer Aamer Jamal was batting on 45 from 65 balls, hitting four fours to strengthen MIT Solutions’ position latter in the innings.

With him at the other end was Salman Aslam who is yet to open his account.

Opener Mohammad Farooq made 22 off 27 balls with three fours before being removed by Test pacer Mohammad Abbas.

Abbas, who remained wicket-less in the first innings, was SBP’s most successful bowler, taking 3-54. Siraj Uddin claimed 2-71.

Earlier in response to MIT Solutions’ first innings score of 112, SBP resumed their innings at 138-6 and were folded for 172 in 44,4 overs to secure 60 runs lead.

Siraj Uddin remained not out on 32 which came off 34 balls and had three glorious fours.

Test-discard Aamer Jamal, who had taken six wickets on Tuesday, finished the innings with 7-32 in 14 overs.

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