Indian Premier League: Hyderabad rain on Delhi’s parade

Sunrisers successfully chase reduced target of 43 in the fifth over.


News Desk May 10, 2014
Hyderabad beat Delhi by eight wickets in a match hampered by rain. PHOTO: BCCI



Sunrisers Hyderabad defeated Delhi Daredevils by eight wickets in a rain-curtailed match as they chased a revised target, according to the D/L method, of 43 runs in five overs, in an Indian Premier League (IPL) match played in Delhi.


Delhi were sent in to bat first and scored 143-7 against a quality Hyderabad bowling side, courtesy Dinesh Karthik (39) and Kevin Pietersen (35). Rain stopped play for about an hour when Delhi were 103-3 in 13.1 overs but the match continued after that without any loss of overs.

Man-of-the-match Dale Steyn, Moises Henriques and Amit Mishra accounted for two batsmen each.

Later, Hyderabad’s innings was interrupted by rain which saw them chasing a revised target of 117 in 15 overs. But rain again stepped in again when they were 11-0 in 1.1 overs, forcing another revised target of 97 off 12 overs.

Rain inflicted a last stab on the match at the conclusion of the second over with 17-1 on board. A final revised target of 43 runs in five overs was posted for Hyderabad to chase.

With three overs and 26 runs to chase, David Warner and Naman Ojha saw Hyderabad to victory with four balls to spare and two important points earned.

Chennai won’t host IPL this year

Chennai will not host any of the four scheduled IPL matches this year due to a dispute with the municipal authorities over the use of three stands at the MA Chidambaram Stadium, according to ESPN.

“There will be no IPL matches in Chennai this year, even the playoffs,” said , Tamil Nadu Cricket Association Secretary Kasi Viswanathan.

Published in The Express Tribune, May 11th, 2014.

Like Sports on Facebook, follow @ETribuneSports on Twitter to stay informed and join in the conversation.

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