IPL
138

IPL 2025: CSK Reaffirms Trust in Mukesh Choudhary After Injury Layoff in IPL 2025

Mukesh Choudhary, the left-arm pacer, has returned to the IPL after being acquired by Chennai Super Kings (CSK) for his base price of INR 30 lakh at the 2025 mega auction. Following an injury setback in 2023 and limited opportunities in 2024, the 28-year-old aims for a steady comeback with CSK.

Mukesh Choudhary has returned to the IPL after being acquired by CSK.
Image: Mukesh Choudhary has returned to the IPL after being acquired by CSK / © NDTV Sports

Mukesh Choudhary, a promising left-arm pacer known for his ability to swing the ball, has found his way back to the IPL fold after being signed by Chennai Super Kings at his base price of INR 30 lakh during the 2025 IPL mega auction. The 28-year-old, who has shown glimpses of brilliance in his IPL career, will look to make a strong performance to draw attention of IPL fans after a few challenging seasons.

Choudhary made an impactful debut in the 2022 IPL season for CSK, picking up 16 wickets in 13 games and emerging as a dependable bowler during powerplays. However, an unfortunate injury ruled him out of the 2023 season, putting his career momentum on hold. In 2024, he returned to the CSK squad but managed to feature in just one game without any wickets to his name.

In domestic cricket, Choudhary represents Maharashtra and has recently regained form in the ongoing Ranji Trophy. His standout performances in the last three matches, where he bagged 15 wickets, have caught the selectors’ attention and showcased his readiness for high-pressure games.

With CSK placing faith in him once again, Choudhary will aim to recapture his 2022 magic and strengthen their bowling attack. His return to the IPL represents a second chance to solidify his position as a key performer in one of the league’s most successful franchises. This could become a win-win situation for both of him and the franchise as they will look upto him in the powerplay to have some early wickets.

Comments

Thank you! We’re reviewing your comment.
We were unable to post your comment. Please, try again.