TODAY’S PAPER | January 31, 2026 | EPAPER

Pakistan opt to bat after winning toss in 2nd Australia T20I

Both sides make multiple changes to their playing XIs


Web Desk January 31, 2026 1 min read
PHOTO: EXPRESS

Pakistan won the toss and chose to bat first against Australia in the second T20 international at Gaddafi Stadium in Lahore on Saturday.

Both sides made multiple changes to their playing XIs, with Pakistan bringing in Naseem Shah, Faheem Ashraf and Usman Tariq in place of Fakhar Zaman, Shaheen Afridi and Salman Mirza.

Australia made four changes to their side, including the inclusion of captain Mitchell Marsh, along with Josh Inglis, Sean Abbott and Matthew Kuhnemann.

The match forms part of the ongoing T20 series between the two teams.

Read: Ayub star in Pak T20 win over Australia

In the first T20I, all-rounder Saim Ayub starred in Pakistan's spin-assisted 22-run win over Australia.

Ayub top-scored in Pakistan's 168-8 with a 22-ball 40 that included two sixes and three fours, while Salman Agha added four sixes and a four in his 27-ball 39.

The tourists managed 146-8 in their 20 overs, with spinners taking six wickets for Pakistan.

With the ball, Ayub dismissed Australian openers Matthew Short (five) and Travis Head, who hit two sixes and two fours in his 13-ball 23.

Cameroon Green resisted with a 31-ball 36 but Australia succumbed to spin with Abrar Ahmed taking 2-10 while Mohammad Nawaz and Shadab Khan took a wicket apiece.

Both teams are tuning up for the Twenty20 World Cup starting in India and Sri Lanka from February 7.

Playing XI

Pakistan: Saim Ayub, Sahibzada Farhan, Salman Ali Agha (c), Babar Azam, Usman Khan (wk), Shadab Khan, Muhammad Nawaz, Faheem Ashraf, Naseem Shah, Usman Tariq, Abrar Ahmed

Australia: Mitchell Marsh (c), Travis Head, Cameron Green, Josh Inglis (wk), Matthew Renshaw, Cooper Connolly, Matthew Short, Xavier Bartlett, Matthew Kuhnemann, Adam Zampa, Sean Abbott

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