Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Aug 24, 2019, 11:50 PM (IST)
Edited: Aug 24, 2019, 11:50 PM (IST)
India lost both their openers – Mayank Agarwal and KL Rahul – and Cheteshwar Pujara but managed to extend their lead to 173 at tea on day three of the first Test against West Indies at the Sir Vivian Richards Stadium, North Sound in Antigua on Saturday.
Skipper Virat Kohli and deputy Ajinkya Rahane were batting on 14 and 5 respectively before the second session came to an end.
West Indies managed to dismiss Mayank Agarwal shortly after lunch as Roston Chase trapped the Indian opener before the stumps.
While Rahul and Pujara added 43 runs together to push India past 70-run mark, Rahul perished as Chase, who dismissed the Indian openers for the second time in the match, scalped his second wicket of the innings.
Pujara was the next man to get out as Kemar Roach let one sneak through Pujara’s bat and pad to disturb the timer. Having picked up four wickets in the first innings, this was Roach’s fifth wicket in the series opener.
Earlier, India bowled out West Indies for 222, securing a 75-run lead in the first innings. West Indies resumed the day on the overnight score of 189/8.
India were looking for early strikes but skipper Jason Holder and Miguel Cummins denied India that opportunity as the two added 41 runs. Shami broke the partnership as he dismissed Holder before Ravindra Jadeja ended Cummins’ 95-minute 45-ball duck inning, second longest duck in Test cricket, to end West Indies’ innings for 222.
Brief scores:
Second innings: India 98/3 (KL Rahul 38; Roston Chase 2/42) vs West Indies
First innings: India 297 all out (Ajinkya Rahane 81, Ravindra Jadeja 58; Kemar Roach 4/66) vs West Indies 222 all out (Roston Chase 48, Jason Holder 39; Ishant Sharma 5/43)
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.