Wahab Riaz leaves Essex for national duty

Left-armer is set to join Pakistan's training camp at Hampshire’s Ageas Bowl for two-week conditioning camp


APP June 24, 2016
Wahab Riaz (L) celebrates with teammates at the Shere Bangla National Cricket Stadium in Dhaka on May 8, 2015. PHOTO: AFP

ISLAMABAD: Left-arm pacer Wahab Riaz’s spell at Essex has been cut short by two games after he was required to join Pakistan’s training camp ahead of the Test series against England.

The 30-year-old left-arm bowler was signed as Essex’s second overseas player, alongside New Zealand’s Jesse Ryder, for the first seven games of NatWest T20 Blast. Kiwi bowler Adam Milne is expected to replace Wahab for the final seven games.

Essex are currently at the bottom of the South Group, having won one of five games in the tournament, and have been looking for a replacement overseas signing, according to ESPNCricinfo.

English batsmen will be tested by our bowlers, says Wahab Riaz

Although Wahab only managed to take four wickets in five matches, at an average of 46.50 and with an economy rate of 9.45, he said he enjoyed his time at Chelmsford. The left-armer could return if Essex manage to turn things around and reach Finals Day.

“It was wonderful to be part of the Essex team,” he said. “I have enjoyed a lot here, and it’s been fun playing with these guys,” he added.

Wahab to bank on Essex experience for England tour

The fast bowler further said he hopes Pakistan will benefit from his experience at Essex. “I have learned a lot here, bowling in these conditions, so hopefully the experience I am taking from Essex will benefit my bowling in the upcoming Tests,” he said.

Riaz, who has played 15 Tests, 69 one-day internationals and 20 T20Is for Pakistan, will join the national squad which is currently based at the Hampshire’s Ageas Bowl to undergo a two-week conditioning camp before the first tour game against Somerset on July 3.

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