Day one talking points from first Pakistan-South Africa Test

No dropped catches, spinners dominating and a lot more happened on day one of first Pakistan-South Africa Test


Abdul Majid January 26, 2021
PHOTO COURTESY: PCB

print-news
KARACHI:

The long-awaited clash between South Africa and Pakistan finally started at the National Stadium of Karachi and the hosts were dominant on the first day of the first Test courtesy the bowlers.

South Africa opted to bat first with the plan of posting a big first innings total on their mind. They attacked the Pakistani bowlers during the first hour and bagged quite a lot of boundaries.

But Pakistan struck back after lunch courtesy 34-year-old debutant Nauman Ali, who reaped the rewards of the pressure created by his spin partner Yasir Shah.

Some might also say that South Africa shot themselves in the foot with two unwanted run-outs, however, the pressure created from Pakistan also played a major role as the visitors’ bundled out for 220.

1. Where was Nauman Ali all this time?

With 285 wickets in 79 first-class matches, Nauman Ali’s non-selection before this series seems nothing less than criminal.

He had a case to prove for his selection in the final XI and made sure he was Nauman economical as well as clinical with his slow left-arm deliveries.

His 17 overs where he bagged two wickets for 38 runs proved to be important as Yasir was doing the damage on the other end.

It also reminded one of the partnership between Yasir and Zulfiqar Babar in the earlier days of Pakistan playing their home fixtures in the UAE. It won’t be wrong to say that Pakistan have once again found a striking spin partner to assist Yasir.

2. Pakistan’s catching and fielding

They didn’t drop any on day one to put it precisely and they took nearly all the chances that came their way. Only one catch in the slip squadron was not taken and the jury agrees that it bounced short on the fielder.

Other than that, Pakistan were above average in the fielding and catching department, if compared with their performance in New Zealand, where they caught less and dropped more.

3. High-flying Shaheen

Shaheen Shah has metamorphosed from just a quick teenager to the leader of the bowling pack in a very short time for Pakistan.

The left-arm quickie is the first choice pacer in all formats now and is also given the new ball to open the bowling for Pakistan and to be honest, he has earned all that trust.

In the most recent series against New Zealand, he was exceptional and would’ve bagged more wickets if catches were taken off his bowling. Meanwhile, on day one against South Africa on the National Stadium turf, Shaheen was once again outstanding.

On a spinner’s heaven, Shaheen bagged two wickets in his 11.2 overs for 49 runs.

4. Flashy, but ineffective Hasan

Hasan Ali was brought back into the national fray on the basis of one good Quaid-e-Azam Trophy season and his dry spells proved why Tabish Khan should have been selected instead.

Hasan was seen in action in Pakistan colours after a long time on Tuesday, but everyone would agree that he seemed like the shadow of the bowler who was on fire during the 2017 Champions Trophy.

His 14 overs produced only one wicket, while he leaked away 61 runs to accumulate the highest economy among Pakistani bowlers.

It can be said that he will need time to adjust to the pressures and rigours of international cricket, but it can also be said that he may have lost the Midas touch which made him a special bowler. Only time will tell what is true.

5. Batting flop

South Africa may have lost the plot in batting but they were on target when they came out to bowl and dismissed more than the desired number of Pakistani batsmen, including Babar Azam, to turn the tide of the match in their favour in the final hour of the day.
The idea of failing in batting on foreign soil is not alien, but faltering on home soil made Pakistan look erratic. Fingers crossed for day two.

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