Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Aug 14, 2015, 02:35 PM (IST)
Edited: Aug 14, 2015, 02:35 PM (IST)
Mayank Agarwal, the prolific opener for India A, looked his usual belligerent self in his short innings of 32, but his rampage was cut short by a bizarre run out to have India A losing their first wicket in their chase of 227 against Australia A in the tri-series final in Chennai. He was attempting to complete a tight single with his opening partner, Unmukt Chand, and would have been home safely had he not jumped to avoid the throw, which struck the wickets and had him out as he had been inside the crease but in the air. LIVE UPDATES: India A vs Australia A, final, A-team Triangular Series, Chennai
It seemed a run-out would have been the only way Agarwal could have been tamed. Two centuries and a fifty in the tournament have made him the highest run-getter, leading Joe Burns by more than 100 runs. His century against South Africa A on Thursday took India A to an mammoth total of 371, and he looked similarly confident and capable of a big one today.
His highlight was a six hit off fast bowler Nathan Coulter-Nile straight down the ground, which was nothing more than a sweetly lofted cover drive with minimal foot movement. On the next ball, he mistimed Coulter-Nile to third man in another attempted big hit, this time with one knee down to get leverage.
His wicket, in the ninth over, was against the run of play, as the home team were going confidently at 59 for no loss. But it turned out to be a turning point, at least temporarily, as two more wickets fell, that of the set Chand, and Karun Nai, fairly quickly after that.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.