Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Aug 14, 2015, 04:23 PM (IST)
Edited: Aug 14, 2015, 04:23 PM (IST)
Gurkeerat Singh, the middle-order batsman for India A, has batted patiently and cautiously for a half-century to help lead a recovery in the team’s chase of 227. Among his four fours scored were three straight drives past the bowler: two off seamer Gurinder Sandhu, and one off Nathan Coulter-Nile. His third four off Sandhu was a streaky one. But his innings was not reliant on boundaries — he has taken half of his runs via singles, and eight via doubles. His partnership with Akshar Patel, and later Sanju Samson, at run-rates of reasonably above 4.50 per over, has given India A a strong chance of clinching the final. LIVE UPDATES: India A vs Australia A, final, A-team tri-series, Chennai
The opening duo of the home side took off briskly to gather 59 runs before Mayank Agarwal, the aggressor, got run out in a strange fashion. His opening partner Unmukt Chand had played the ball to cover, and while completing the run, Agarwal leaped at the final stride that would take him into the cease, to avoid the throw. At the moment the stumps were broken by the direct throw, Agarwal was inside the crease but in the air.
Wickets stated to fall regularly thereafter. From 59 for 0, India A were reduced to 65 for 3. Brief partnerships ensued, but there wasn’t any permanence. Stalwarts Manish Pandey and Kedar Jadhav were removed before they could settle down to take the opposition bowling down. In the 29th over, Patel, after negotiating a careful period, decided to pull Gurinder Sandhu hard, but provided a top edge to midwicket.
Gurkeerat, however, was the calming factor despite the wicket, and with Sanju Samson, he steered India A in a responsible manner.
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.