IPL 2025: CSK Playing XI vs PBKS- Match 22

Published - 08 Apr 2025, 11:00 AM | Updated - 08 Apr 2025, 03:00 PM

Chennai Super Kings (CSK).
Chennai Super Kings (CSK). Image Credit: X

The Chennai Super Kings (CSK) made a thumping start in the Indian Premier League (IPL) 2025 with a powerful victory at the MA Chidambaram Stadium against the Mumbai Indians.

But since then, the brigade has fallen to the five-time champions. They failed to chase the 190+ score at home against the Royal Challengers Bengaluru, who earned their very first victory in Chennai, beating the Super Kings in 2008.

MS Dhoni tried hard along with Ruturaj Gaikwad, the leader, but they couldn’t collect the win against the Rajasthan Royals at the Barsapara Cricket Stadium in Guwahati. And then Delhi blew CSK away for their first victory against this opponent since 2010 in Chennai.

IPL 2025: CSK Playing XI vs PBKS- Match 22

Openers- Rachin Ravindra and Devon Conway

Rachin Ravindra started the IPL 2025 campaign well with a half-century to his name against the Mumbai Indians. The left-handed batter was decent in the run chase against the RCB side, but since then, the youngster hasn’t stood up to his performance.

Against the Royals, he got on a four-ball duck before struggling at home against Delhi. Ravindra wanted to close the bat face on a slow Chennai surface against Mukesh Kumar to get a leading edge into the hands of the bowlers.

CSK tried Devon Conway at the opening stand but didn’t get the desired result. They have to find a way to get something from the opening pair against the Punjab Kings.

Also Read: “Tilak Verma Would Be Devastated”- Ex-India Coach Crushes Mumbai Indians

Middle Order- Ruturaj Gaikwad (c), Shivam Dube, Vijay Shankar, Ravindra Jadeja, Shaik Rasheed/Rahul Tripathi, MS Dhoni (wk.)

The CSK captain, Ruturaj Gaikwad, was confident after his half-century in the previous contest. But again, he was undone by the pace of the bouncer against Mitchell Starc and couldn’t keep the ball in the park, just like he was trapped by Hazlewood on the second encounter.

Shivam Dube also went through the same journey. He nailed the first ball for a six against Viraj Nigam and sliced the very next ball in the air as Tristan Stubbs grabbed a great catch. The management will be happy with Vijay Shankar getting a fifty and bandaging the fall of wickets.

Rahul Tripathi may also come in the middle order if the CSK side wants to go with an extra batter. Else, they could use the young batter, Shaik Rasheed. MS Dhoni came early in the game against Delhi but lacked intent in a huge run chase from the start.

Bowlers: Noor Ahmed, Ravichandran Ashwin, Khaleel Ahmed, Matheesha Pathirana

Ravichandran Ashwin bowled well in the first innings, scoring 0/21 in three overs, but he didn’t complete his full four-over quota. This also happened with Ravindra Jadeja and Noor Ahmed. The latter was excellent for CSK by then, but went for plenty as KL Rahul smacked him for a few fours and sixes in the second innings.

Khaleel Ahmed bowled well for his powerplay wicket with the new ball as he trapped Jake Fraser-McGurk in the cage for his only wicket of the fixture. Matheesha Pathirana, known for his death overs bowling, used his pace and variations beautifully against Delhi and should play the next game for CSK against Punjab.

Mukesh Choudhary may not play the game in Chandigarh as he went for 50 runs in his four overs without any success. The focus will also be on Gaikwad’s leadership.

CSK Predicted Playing XI vs PBKS- Match 22

Devon Conway, Rachin Ravindra, Ruturaj Gaikwad (c), Shivam Dube, Vijay Shankar, Ravindra Jadeja, Shaik Rasheed/Rahul Tripathi, MS Dhoni (wk), Noor Ahmed, Ravichandran Ashwin, Khaleel Ahmed.

Impact Sub: Matheesha Pathirana.

Also Read: Ex-India Players Tear Apart Hardik Pandya After His Cunning Act vs Tilak Varma

Tagged:

Punjab Kings Chennai Super Kings PBKS vs CSK IPL
logo
Stay Updated with the Latest Cricket News from OnCricket.

You will receive the latest updates on cricket news throughout the day. You can manage them whenever you need in browser settings.