T20 World Cup 2024: Pakistan’s likely playing XI against Canada

Pakistan is gearing up for a must-win clash against Canada.

Sports Desk June 11, 2024

Pakistan is gearing up for a must-win clash against Canada on June 11 at Nassau County International Stadium in New York. Following a disappointing defeat to India, Pakistan finds itself in a precarious position, currently near the bottom of Group A with two losses from two matches.

The recent loss to India exposed significant issues in Pakistan's batting lineup, despite a commendable effort from their bowlers who managed to restrict India to just 119 runs. The middle order's failure, particularly from Iftikhar Ahmed and Shadab Khan, has raised concerns.

With talented players like Saim Ayub waiting for an opportunity, Pakistan may consider making strategic changes to strengthen their batting order. Saim Ayub is likely to replace Shadab Khan in the playing XI, given Shadab's struggles with both bat and ball.

The pitches in New York have favored bowlers, with no team scoring more than 150 runs, the highest being 137. With clear skies forecasted, the pitch is expected to remain bowler-friendly.

Pakistan is expected to continue with four pacers on the challenging New York pitch. Although Imad Wasim returned from injury against India, he struggled with his running while batting. If Imad is unavailable, Pakistan might select Abrar Ahmed as their sole specialist spinner.

The match, scheduled for 7:30 pm (PST), promises a thrilling contest between bat and ball as both teams vie for a crucial win in their T20 World Cup campaign.

Likely XI:

• Saim Ayub
• Mohammad Rizwan (wk)
• Babar Azam (c)
• Usman Khan
• Fakhar Zaman
• Iftikhar Ahmed
• Imad Wasim/Abrar Ahmed
• Shaheen Afridi
• Mohammad Amir
• Haris Rauf
• Naseem Shah

With the stakes high and the pressure mounting, Pakistan will need to bring their best game to secure a victory and keep their T20 World Cup hopes alive.


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