Two-week break: Finch backs rusty Australia against NZ

Co-hosts to meet on Saturday; Kangaroos have not played since Feb 14.


Afp February 23, 2015
Finch, who scored 135 in the Melbourne romp against England, said the two-week break will not be an issue when the two Pool A rivals meet at Auckland’s Eden Park. PHOTO: AFP

AUCKLAND: In-form opener Aaron Finch shrugged off concerns that a rusty Australia will be caught cold by high-flying trans-Tasman rivals New Zealand on Saturday in what will be their first World Cup match in two weeks.

The Black Caps have won three games while Australia, who started their campaign with a thumping 111-run victory over England on February 14, saw their second match against Bangladesh abandoned due to heavy rain without a ball being bowled in Brisbane last weekend.

Finch, who scored 135 in the Melbourne romp against England, said the two-week break will not be an issue when the two Pool A rivals meet at Auckland’s Eden Park.

“We came off a good game against England and we’ve had no problems really,” said Finch of the game on February 14 — the opening day of the six-week World Cup. “We’ve been training well during the week and had a pretty solid session on Saturday when we were meant to play. We’re feeling good and ready to go.”

Surprisingly, the 28-year-old Finch has never played an ODI against New Zealand despite making his debut in January 2013 and having notched up 42 games. That is due to the fact that Australia’s last one-dayer against New Zealand was in the 2011 World Cup, while a game in the Champions Trophy in England two years later was called off due to rain.

The game will probably decide who tops the pool and meets a relatively weaker team from Pool B in the quarter-finals.

Published in The Express Tribune, February 24th, 2015.

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