PBKS vs RR, IPL 2024: Rajasthan Royals Brave Accurate Punjab Kings Bowlers, Slow Pitch To Register Three-Wicket Win


Rajasthan Royals struggled against the Punjab Kings bowlers, who smartly controlled the pace of the ball on a sticky pitch, but found enough stamina to pull out a hard-fought three-wicket win in their IPL 2024 match in Mullanpur on Saturday . The target of 148 seemed easy, but the presence of Punjab bowlers and the firm surface made the Royals' task difficult before they reached 152 for seven. Rajasthan needed 49 runs in the last five overs, but despite having power-hitters like Rovman Powell (11, 5b) and Shimron Hetmyer (27 not out), they had to wait till the last ball of the match. 10b, 1×4, 3×6) in their ranks.

The equation came down to 10 in the last six balls after Hetmyer hit a six and a four off Harshal Patel, which the West Indies left-handed batsman realized through two sixes off fast bowler Arshdeep Singh in the last over.

Royals started their chase through Yashasvi Jaiswal and Tanush Kotian without any real scoreboard pressure.

However, Kotian, who was batting so high up the order for the first time in T20, could not find his flow but still helped Jaiswal add 56 runs in 8.2 overs.

But his attempt to ground Liam Livingstone resulted in him losing his leg-stump.

Jaiswal, who played a brilliant flick on the ball of Kagiso Rabada, is on the way to end the streak of low scores in this IPL.

But an unnecessary uppercut off Rabada's ball was caught by Harshal Patel at third man, due to which Rajasthan's position looked a bit shaky.

Their trouble deepened when captain Sanju Samson, who had earlier eased livingstone's troubles by hitting a six and a four, was LBW off Rabada in his last over.

Samson could not connect with Rabada's slightly low, inbound ball and the ball hit his backfoot and even DRS could not save him.

Earlier, Rajasthan bowlers, led by Avesh (2/34) and Maharaj (2/23), made the most of the sticky pitch to restrict Punjab Kings to a huge score.

Ashutosh Sharma (31, 16b), Jitesh Sharma (29, 24b) and Livingstone (21, 14b) tried to push the pace, but Punjab needed more than those short cameos.

But Kings' innings had a very fast start and 26 runs were scored in the first three overs as Atharva Tayde, who came in place of injured captain Shikhar Dhawan, hit two fours off fast bowler Kuldeep Sen.

But the brakes were soon applied as Tide's mistimed pull of Avesh's ball ended up in Sen's hands inside the circle.

After this, Punjab's batsmen struggled to get any kind of pace on a pitch which was a bit difficult, especially for left-arm spinner Maharaj and leg spinner Yuzvendra Chahal.

However, some credit must also be given to veteran fast bowler Trent Boult who conceded just 15 runs in his three power play overs.

Kings got only 10 runs in the last three power play overs as they ended that run at a modest score of 38 runs for one wicket.

Over the next five overs, the hosts struggled to hit even a single boundary as they reached 53 for four in 10 overs, losing Jonny Bairstow, stand-in-skipper Sam Curran and Prabhsimran Singh, all slow A combination of decks devoured and precision spinners.

Their biggest hope may have been the range-hitting ability of in-form Shashank Singh, but a weak pull from Sen could not get past Jurel at mid-wicket.

With the top order failing to contribute anything significant, PBKS needed some big hands from Livingstone and Jitesh to reach the even score.

Sharma also showed some intent, timing Chahal brilliantly to hit a six in the extra over, and later hitting Sen for a six straight over the fence before dismissing Avesh.

Livingstone, who hit a six and a four off Sen's consecutive balls through mid-wicket, and Ashutosh, who hit two sixes off Avesh in the 19th over, helped PBKS add 61 runs in the last five overs, but their efforts were of little use. Remained weak. Late.

(Except for the headline, this story has not been edited by NDTV staff and is published from a syndicated feed.)

Topics mentioned in this article

Related Post

Leave a Reply

Your email address will not be published. Required fields are marked *