Cricket News

‘A perfect tribute to RCB’ – Fans celebrate as CSK thrash KKR by 49 runs in IPL 2023

This is Kolkata Knight Riders’ fourth consecutive loss in the ongoing IPL 2023.

Published on

Kolkata Knight Riders vs Chennai Super Kings in IPL 2023 (Image Credit: Twitter/IPL)

In the 33rd game of the ongoing IPL 2023, Kolkata Knight Riders played host to Chennai Super Kings. Ahead of the game, the home team was coming off three back-to-back losses in the tournament and has only two wins in six games. On the other hand, CSK had four wins in six games and was coming off two back-to-back wins.

Meanwhile, in this game, the two-time winners, Knight Riders won the toss and elected to bowl first. This decision turned out to be a nightmare for the former champions. Apparently, the likes of Devon Conway and Ruturaj Gaikwad provided a great start with 73 runs in 7.3 overs. The latter was the first wicket to fall after scoring 35 off 20 balls. At this stage, in-form Ajinkya Rahane came out to bat.

Even though his partnership with Conway was slow (36 off 28), the former made up for it with Shivam Dube. After Conway got out at the individual score of 56 off 40 balls, Dube came and started the carnage in no time. He and Rahane put together 85 runs off just 32 balls. While Dube scored 50 off 21 balls, Rahane scored 71 not out off 29 balls. Ravindra Jadeja (18) also put his hand up and the team reached 235/4.

Kolkata Knight Riders’ middle order tried their best but it wasn’t to be

In reply, the Purple Brigade got off to a poor start as they lost three wickets for 46 runs. With the fall of wickets, the required run rate was ever increasing with Jason Roy couldn’t open the batting due to an injury. After the fall of the third wicket in the form of Venkatesh Iyer, Roy came out to bat.

At the time, the team needed 190 runs in 12.5 overs. The 2019 World Cup winner tried his best with 61 off 26 balls including five fours and as many sixes. The hero against Gujarat Titans, Rinku Singh (53*) also tried his best but the required run rate was pretty much out of reach, not mathematically though. In the end, the team lost the game by 49 runs.

This is how Twitter reacted

66 Comments

Popular Posts

Exit mobile version