"You expect someone who has played 40 balls to have a better strike rate": Pathan criticises Jurel's knock in RR's loss
Mumbai, May 18
After the Rajasthan Royals loss against the Delhi Capitals, former Indian all-rounder Irfan Pathan criticised wicketkeeper-batter Dhruv Jurel for his knock, saying that he could have batted with a better strike rate and helped RR cross the 200-run mark.
Half-centuries from Riyan Parag and Dhruv Jurel were not enough as a sensational four-wicket haul from Mitchell Starc pushed RR from 160-odd at loss of two wickets to a score of 193/8 in 20 overs, which the Capitals chased down comfortably with fifties from KL Rahul and Abhisek Porel, registering their second loss at home in seven games and ending the Arun Jaitley Stadium leg of their run on a high after five horrific losses.
Jurel played a crucial knock of 53 in 40 balls, with five fours and two sixes, before perishing to Lungi Ngidi as the eighth wicket after a while of battling wickets falling at the other end. His fifty contrasted with skipper Riyan Parag's 26-ball 51, which had three fours and five sixes and an SR of almost 200.
Speaking on his YouTube Channel, Pathan was critical of Jurel's approach, saying, "Rajasthan scored just 33 runs from the last six overs. Dhruv Jurel is a good batter, but scoring 50 runs off 40 balls, you expect someone who has played 40 balls to have a better strike rate. That was a mistake, and because of this, they could not cross 200," he said.
Jurel is enjoying his best IPL with the bat, scoring 367 runs in 12 matches at an average of 33.36 and a strike rate of over 151, with four fifties and a best score of 81*, but a lack of impactful runs in some matches has been a concern.
Coming to the match, DC won the toss and opted to bowl first. After the early dismissal of Yashasvi Jaiswal, Vaibhav Sooryavanshi (46 in 21 balls, with five fours and three sixes) and Dhruv Jurel put on a 70-run stand. Later, Jurel also provided support to skipper Riyan Parag, who registered his second fifty this season with 51 in 26 balls, with three fours and five sixes. But from 162/2, RR collapsed to 193/8 in 20 overs, with Mitchell Starc (4/39), Lungi Ngidi (2/24) and Madhav Tiwari (2/27) tightening the screws.
During the chase, Abhisek (51 in 31 balls, with seven fours and a six) and KL Rahul (56 in 42 balls, with a four and three sixes) put on a 105-run stand, after which they sank to 153/4. Knocks from skipper Axar Patel (34* in 18 balls, with two fours and two sixes) and Ashutosh Sharma (18*) finished off the chase with five wickets and four balls in hand.
DC is in seventh place, with six wins and seven losses, giving them 12 points. RR is placed fifth, with six wins and six losses, giving them 12 points.
— ANI
Reader Comments
Honestly, I think Pathan is being a bit harsh. Jurel was anchoring the innings after early wickets – Vaibhav fell, Parag needed time. He got a fifty, held one end. The real problem was the collapse from 162/2 to 193/8. Blaming only Jurel is unfair. 😊
As an outsider looking in, it's fascinating how passionate Indian fans are about these small details. Pathan's point is valid: in T20, you need maximum damage. But Jurel's 53 off 40 might have been crucial if others had supported him better. It's a team game after all.
Exactly why IPL analysis in India is next level! Pathan knows his cricket. Jurel's SR of 151 is good overall, but today, with wickets falling, he should've taken more risks. 33 runs in last 6 overs is criminal. Starc was brilliant though!
I partially agree with Pathan, but let's also credit DC's bowling. Starc, Ngidi, and Tiwari bowled tight lines and squeezed RR. Jurel is only 23, still learning. At least he got a fifty and is having his best IPL season. Respect that!
Interesting debate. In the US, we'd say Jurel played his role - got a fifty and held the innings together. But in T20, you need those big overs. I think both Pathan and the defenders have valid points. At the end of the day, RR's middle-lower order failed collectively
We welcome thoughtful discussions from our readers. Please keep comments respectful and on-topic.