Finch Set For Scans After Hamstring Twinge in T20 World Cup Win
Cricket Stadium And Wickets

Aaron Finch will undergo scans on Tuesday after hurting his hamstring in Monday’s 42-run win over Ireland at the T20 World Cup where he re-discovered some form.

Finch blasted 63 from 44 balls at the top of the Australia order, but left the field during his side’s bowling innings as Ireland were bowled out for 137, chasing 180 for victory.

The Australia skipper had been in poor form, leading to questions about his spot in the side, but having shown some good touch, the injury comes at a bad time, with the hosts scrapping for a spot in the semi-finals.

“I’ve had a bit of a hammy twinge,” Finch said. “I don’t feel too bad at the moment but generally overnight it can stiffen up a bit

“Let’s see how it goes, will have a scan tomorrow.”

Finch battled to an unbeaten 31 from 42 balls in Australia’s win last week over Sri Lanka, mounting the pressure on him.

In response to the pressure, he said: “Nah, not feeling the pressure at all to be honest.

“The support from the change room and support staff has been incredible. T20 is a high risk-game, sometimes it comes off, sometimes it doesn’t.”

Finch was named Player of the Match, leading Australia’s charge with 5-179, with contributions from [[Marcus Stoinis] (35 from 25) and Mitchell Marsh (28 from 22).

“Wasn’t the easiest wicket, lot slower than we thought it was be,” Finch added. “They bowled well, cutters and stuff, was hard to get into rhythm.

“It wasn’t easy to come out and go after the bowling from the start.”

Australia moved up to second in Group 1 with the win but will be hoping leaders New Zealand account for England on Tuesday. Australia’s next game is against Afghanistan on Friday.

Ben somerford
Sports Pundit staff writer @bensomerford
Australian journalist who specialises on all sports, focusing on football, tennis, basketball and racing, having written for global publications including FourFourTwo, AAP, Inside Futbol and many more....

Comment on This Article

0 comments
Reply to