Babar Azam has been recalled to Pakistan's Test squad ahead of the series against South Africa, set to begin on December 26 at SuperSport Park, Centurion.
The right-handed batsman, who has not featured in the Test team since October 2024 due to a prolonged poor run of form, will replace out-of-form opener Abdullah Shafique.
Babar, who is just three runs away from reaching the 4,000-run milestone in Test cricket, has been struggling for consistency in the longest format since his last significant score of 161 runs against New Zealand in December 2022.
Over the past 18 Test innings, he has managed only 366 runs, with his best score during this period being 41 runs in the second innings against Australia in Melbourne, December 2023.
Sources confirmed that Babar, despite these struggles, will return to bat at number three in the lineup. This marks a significant development, given that the Pakistan team management and selection committee have decided to include him in the squad for the first Test against South Africa, following his solid performances in the recent ODI series.
Babar scored 148 runs in the series, including two half-centuries, and demonstrated the form needed to make a comeback to the Test team.
In a further reshuffle, Abdullah Shafique, who was dismissed for a duck in all three ODIs against South Africa, has been dropped from the squad.
To fill the gap, Shan Masood, who is currently batting at number three, will open the innings alongside young talent Saim Ayub, according to media reports.
Masood has ample experience in the opening position, having started his Test career as an opener. With 38 Test caps and a history of opening the innings in 46 of his 72 Test innings, Masood is well-equipped to take on this responsibility once more. He has scored four centuries and five half-centuries as an opener.
This squad change comes at a crucial time for Pakistan, who are looking to bounce back after a series of mixed results.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ