‘Purple Cap nahin Orange Cap jeetega’ – Memes galore after Tushar Deshpande conceded 56 runs in four overs in IPL 2023 final

Chennai Super Kings pacer Tushar Deshpande has had a bad day in the ongoing IPL 2023 final against Gujarat Titans. He had a good start with the ball as he conceded four runs in his first over. During the same over, Deepak Chahar dropped an easy catch of Shubman Gill. As it turned out, the latter hit three back-to-back fours in Deshpande’s second over.

After this, the right-arm pacer was taken off from the bowling attack. On the other hand, the likes of Gill, Wridhiman Saha, and Sai Sudarshan were taking apart CSK’s bowling attack. The trio made the former champions regret their decision to bowl first. Meanwhile, when Deshpande came back to bowl his third, the likes of Gill and Saha had gotten out but the defending champs scored 153/2 in 16 overs.

Sudarshan took apart Deshpande as the former hit six and three fours, all towards the off-side. Notably, there was only one fielder on the off-side, and Deshpande bowled towards the off-side while Sudarshan was moving towards the same side to access the leg side. In his last over, Deshpande was taken for two sixes and a four by the same batter.

Tushar Deshpande is the sixth-highest wicket-taker in the tournament

The former Delhi Capitals has had a mixed season with the ball so far. In some games, the Mumbaikar was taken to cleaner while in some games, he did well with the ball. Now, he has finished with 21 wickets in the tournament. At the top, Gujarat Titans, Mohammed Shami, Rashid Khan, and Mohit Sharma are leading the charts with 28, 27, and 24 wickets respectively.

Mumbai Indians’ Piyush Chawla and Rajasthan Royals’ Yuzvendra Chahal have 21 and 22 wickets respectively. Meanwhile, the fans are trolling Deshpande for his poor bowling performance. His side now needs to chase 215 runs as Sudarshan scored 96 runs before being trapped lbw by Matheesha Pathirana. This will be the biggest chase in IPL history if the Yellow brigade manages to chase it down.

This is how Twitter reacted