Sloppy England scrape through

Netherlands give Strauss' men a run for their money.


Afp February 21, 2011
Sloppy England scrape through

NAGPUR: Error-hit England survived a huge scare to get their World Cup off to a winning start with a six-wicket victory over Netherlands despite Ryan ten Doeschate’s all-round heroics.

South Africa-born ten Doeschate dominated England’s attack in making 119 as Netherlands piled up 292 for six before taking two for 47. But with England captain Andrew Strauss making 88, the Test-playing nation scraped home.

England were cruising at 166 for one before medium-pacer ten Doeschate struck twice in quick succession. Jonathan Trott was stumped for 56 down the legside by wicket-keeper Wesley Barresi and then he bowled Ian Bell (33) middle stump with his final delivery, leaving England needing 52 off the last seven overs with six wickets standing.

The match was back in the balance and England needed 13 off the last 12 balls. But Ravi Bopara lofted medium-pacer Bernard Loots for six over long-off and levelled the scored with four over long-on off the same bowler.He then smashed the next delivery to the boundary as England won with eight balls to spare.

Doeschate provided solid platform

Earlier, ten Doeschate faced just 110 balls and hit three sixes and nine fours as Netherlands, who beat England in the opening match of the 2009 World Twenty20, eyed another upset.

There was no denying both the quality of ten Doeschate’s batting or the ineptitude of England’s display, which included wayward fast bowling, dropped catches, sloppy fielding and ‘wicket’ chalked off when Strauss had too few fielders inside the circle.

Ten Doeschate shared several fifty stands, the best a third-wicket partnership of 78 with Tom Cooper (47). Swann kept things tight as the Netherlands flew the flag for associate nations at this World Cup.

Published  in The Express Tribune, February 23rd, 2011.

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