Connect with us


‘Ashwin sent in to retire out again?’ – Twitter perplexed by RR’s decision during 192-run chase

Rajasthan Royals have pulled a rabbit out of the hat with their tactics yet again. In their game against Gujarat Titans on thursday (April 12), they were in pursuit of 192, and after the first wicket fell in the second over, it was Ravichandran Ashwin who came out to bat for the Royals.

Jos Buttler began in his usual fashion. He took on Mohammed Shami in the opening over, smacking the veteran India pacer for three consecutive fours, reclaiming the Orange Cap from Hardik Pandya. Incidentally, Pandya himself had overtaken Jos Buttler earlier in the match, but held on to the cap only in the space of the innings break.

By the time Devdutt Padikkal took strike for the first time in last ball of the second over, Buttler had already plundered 28 runs off GT’s bowler, having hit five fours and a six. Padikkal was dismissed for a first-ball duck, and it was Ashwin who strolled in to bat at three alongside his old friend Jos Buttler.

The experiment was short-lived; Ashwin only lasted for eight balls, adding eight to the score. It was an entertaining eight balls though, including a huge six off Rashid Khan. But Lockie Ferguson did the trick in the end, Ashwin timed a shot well but couldn’t pierce the field. David Miller took a low diving catch to grab the ball just inches from the ground.

After the last game when Ashwin’s decision to voluntarily retire out sparked a lot of talk, Twitter users were waiting to see how the Royals would handle their batting order this time around. They weren’t disappointed, but many users questioned whether they shouldn’t have sent out a specialist batter considering they were chasing sucha high target.

Twitter had a mixed reaction to Ashwin batting at number three


Click to comment

Leave a Reply

Your email address will not be published.

More in IPL