KKR Playing 11 vs Delhi Capitals- IPL 2024, Match 16

Kolkata Knight Riders (KKR) takes on Delhi Capitals in match 16 of IPL 2024 on Wednesday, April 3. They have won the first two games and are now the only two undefeated teams this season alongside Rajasthan Royals.

Knight Riders won against SRH by four runs and against RCB by seven wickets. They came out with a clinical performance with their batting and bowling both clicking against their arch-rivals.

The only problem for KKR so far has been Mitchell Starc’s lack of form. The Aussie pacer has gone wicketless in the first two games. There have been talks about his pricetag but Bharat Run, KKR bowling coach said that the management believes in Starc and he will return. He went for 100 runs in his 8 overs in the first two games.

The KKR management will hope that Starc strikes form in the next game and the batters and bowlers might keep up with their form. The Knight Riders lost their last three games against DC and they should have clear plans against them heading into the game.

Nitish Rana missed the last match with a finer injury. It will be interesting to see whether he returns. Barring him there are no fitness concerns with the team. After the clinical win over RCB, KKR might play the same XI against Delhi Capitals on Wednesday.

Also Read: Mumbai Indians vs Rajasthan Royals Weather Report Live Today And Pitch Report Of Wankhede Stadium– IPL 2024, Match 14

KKR Playing 11 vs Delhi Capitals- IPL 2024, Match 16

Phil Salt (WK)

Salt will open the batting for KKR. He struck a fifty in his very first game and scored 30 off 20 balls against RCB adding an 86-run stand with Sunil Narine. KKR will hope that he plays in the same fashion.

Sunil Narine

Sunil Narine will open the batting with Salt. Gambhir backed and he delivered against RCB with 47 off 22 balls. It will be interesting to see whether Narine continues his form against DC.

Shreyas Iyer

Iyer will slot in at three. The KKR skipper scored 39 off 25 balls and added a 75-run stand with Venkatesh Iyer in the chase against RCB. He was dismissed for a duck in the first game.

Venkatesh Iyer

Iyer will slot in at four. He scored 50 off 30 balls and helped KKR win the match. It was his eighth IPL fifty for the Knight Riders. He will look to be consistent for the franchise this season. He injured his back while batting against RCB but should be fit to play.

Ramandeep Singh

Ramandeep can bat at five. He scored a quickfire 35 in the match against SRH that gave KKR the momentum in the innings. He was guilty of missing a few catches against RCB.

Rinku Singh

Rinku will slot in at six. He scored 474 runs in the last match for the Knight Riders. Against SRH, he scored a quickfire 23 of 15 balls in the final overs. He needs 245 runs to complete 1000 runs in the IPL.

Andre Russell

Russell will slot in at seven. He did not bat in the last game against RCB but picked up two for 29. He is one short of 100 IPL wickets for KKR and approaching 2500 runs for the side.

Mitchell Starc

Starc can bat at eight. He is under pressure to deliver with the ball after not picking up a wicket in the last two games. KKR roped him in for 24.75 crores. Overall, he has picked up 34 wickets in 29 matches in the IPL. All of his 34 wickets came for RCB.

Anukul Roy

Roy bowled two overs for just six runs in the match against RCB. He has played. He has picked up four wickets in seven games for KKR. He might kept in the playing XI.

Harshit Rana

Rana picked up two for 39 against RCB and so far has picked up five wickets for the franchise. He has bowled with pace so far for KKR.

Varun Chakravarthy

Chakravarthy concludes the likely playing XI for KKR. He bowled just two overs for 20 runs against RCB and went for 55 runs against SRH.

Impact Sub- Suyash Sharma

Suyas Shara might be used as the impact player by KKR. They have used him in that role throughout the last year and it paid rich dividends. KKR used Angkrish Raghuvanshi as the Impact Sub against RCB.

Also Read: Watch: Comedy unfolds as 5 Bangladesh fielders engage in hilarious chase to prevent boundary vs SL