×

Prolonged interruptions, slow over-rate in MI vs RCB pose threats to the very purpose of T20s

“Hardik Pandya, Captain, MI, has been fined for maintaining a slow over-rate. As this was his team’s first offence of the season under Article 2.22 of the IPL’s Code of Conduct, he has been fined Rs 12 lakhs,” the IPL said.

In fact, the contest had players from both teams taking several pauses amid hot and humid conditions. While the first innings ended in two hours and one minute, the second innings finished in two hours and four minutes.

David is said to have not handed over the ball to the umpires twice during RCB’s innings in which the burly Australian scored a quick 16-ball 34 not out with three sixes and two fours.

“The first incident occurred when the umpires changed the ball during the 18th over (17.2) of RCB’s batting innings. He wanted to have a look at the ball and did not hand it over despite being repeatedly asked to do so,” the IPL said.

“The second incident occurred during the 20th over (19.2), when he again did not hand over the ball to the umpires, amounting to repeated failure to comply with the instructions or directives of the umpires,” the IPL said, adding that David has admitted to the offence and accepted the sanction.

Published on Apr 13, 2026

#IPL #Tim #David #fined #breaching #code #conduct #Hardik #Pandya #penalised #slow #overrate"> IPL 2026: Tim David fined for breaching code of conduct; Hardik Pandya penalised for slow over-rate  Royal Challengers Bengaluru all-rounder Tim David was on Monday fined 25 per cent of his match fee and docked one demerit point for “disobeying an umpire’s instruction” during the IPL game against Mumbai Indians.David was guilty of breaching Level 1 of IPL’s code of conduct for players and team officials, while Mumbai Indians skipper Hardik Pandya was also fined for maintaining slow over-rate.The IPL said in a statement that David was found to have breached the Article 2.4 of the IPL’s code of conduct.Pandya was fined after RCB’s innings took a little over two hours to finish.Also read | Prolonged interruptions, slow over-rate in MI vs RCB pose threats to the very purpose of T20s“Hardik Pandya, Captain, MI, has been fined for maintaining a slow over-rate. As this was his team’s first offence of the season under Article 2.22 of the IPL’s Code of Conduct, he has been fined Rs 12 lakhs,” the IPL said.In fact, the contest had players from both teams taking several pauses amid hot and humid conditions. While the first innings ended in two hours and one minute, the second innings finished in two hours and four minutes.David is said to have not handed over the ball to the umpires twice during RCB’s innings in which the burly Australian scored a quick 16-ball 34 not out with three sixes and two fours.“The first incident occurred when the umpires changed the ball during the 18th over (17.2) of RCB’s batting innings. He wanted to have a look at the ball and did not hand it over despite being repeatedly asked to do so,” the IPL said.“The second incident occurred during the 20th over (19.2), when he again did not hand over the ball to the umpires, amounting to repeated failure to comply with the instructions or directives of the umpires,” the IPL said, adding that David has admitted to the offence and accepted the sanction.Published on Apr 13, 2026  #IPL #Tim #David #fined #breaching #code #conduct #Hardik #Pandya #penalised #slow #overrate
Sports news

Prolonged interruptions, slow over-rate in MI vs RCB pose threats to the very purpose of T20s

“Hardik Pandya, Captain, MI, has been fined for maintaining a slow over-rate. As this was his team’s first offence of the season under Article 2.22 of the IPL’s Code of Conduct, he has been fined Rs 12 lakhs,” the IPL said.

In fact, the contest had players from both teams taking several pauses amid hot and humid conditions. While the first innings ended in two hours and one minute, the second innings finished in two hours and four minutes.

David is said to have not handed over the ball to the umpires twice during RCB’s innings in which the burly Australian scored a quick 16-ball 34 not out with three sixes and two fours.

“The first incident occurred when the umpires changed the ball during the 18th over (17.2) of RCB’s batting innings. He wanted to have a look at the ball and did not hand it over despite being repeatedly asked to do so,” the IPL said.

“The second incident occurred during the 20th over (19.2), when he again did not hand over the ball to the umpires, amounting to repeated failure to comply with the instructions or directives of the umpires,” the IPL said, adding that David has admitted to the offence and accepted the sanction.

Published on Apr 13, 2026

#IPL #Tim #David #fined #breaching #code #conduct #Hardik #Pandya #penalised #slow #overrate">IPL 2026: Tim David fined for breaching code of conduct; Hardik Pandya penalised for slow over-rate

Royal Challengers Bengaluru all-rounder Tim David was on Monday fined 25 per cent of his match fee and docked one demerit point for “disobeying an umpire’s instruction” during the IPL game against Mumbai Indians.

David was guilty of breaching Level 1 of IPL’s code of conduct for players and team officials, while Mumbai Indians skipper Hardik Pandya was also fined for maintaining slow over-rate.

The IPL said in a statement that David was found to have breached the Article 2.4 of the IPL’s code of conduct.

Pandya was fined after RCB’s innings took a little over two hours to finish.

Also read | Prolonged interruptions, slow over-rate in MI vs RCB pose threats to the very purpose of T20s

“Hardik Pandya, Captain, MI, has been fined for maintaining a slow over-rate. As this was his team’s first offence of the season under Article 2.22 of the IPL’s Code of Conduct, he has been fined Rs 12 lakhs,” the IPL said.

In fact, the contest had players from both teams taking several pauses amid hot and humid conditions. While the first innings ended in two hours and one minute, the second innings finished in two hours and four minutes.

David is said to have not handed over the ball to the umpires twice during RCB’s innings in which the burly Australian scored a quick 16-ball 34 not out with three sixes and two fours.

“The first incident occurred when the umpires changed the ball during the 18th over (17.2) of RCB’s batting innings. He wanted to have a look at the ball and did not hand it over despite being repeatedly asked to do so,” the IPL said.

“The second incident occurred during the 20th over (19.2), when he again did not hand over the ball to the umpires, amounting to repeated failure to comply with the instructions or directives of the umpires,” the IPL said, adding that David has admitted to the offence and accepted the sanction.

Published on Apr 13, 2026

#IPL #Tim #David #fined #breaching #code #conduct #Hardik #Pandya #penalised #slow #overrate

Royal Challengers Bengaluru all-rounder Tim David was on Monday fined 25 per cent of his…

Bumrah’s wicket-less run an unpleasant confrontation for MI

“A lot of things need ⁠a rethink. But we have to see other options we can have, with the bat and the ball,” Pandya ​said at the ‌post-match presentation.

“We need to still bat and bowl well. If you do that, irrespective of the toss (we should be fine).”

Mumbai’s struggles have been ‌most evident in the PowerPlay.

The lack ​of early wickets and limited support for Bumrah has raised concerns about the ⁠bowling attack, with opponents able to see off the India pacer before targeting the rest.

“Last couple ‌of games, as a bowling and batting unit, we have been catching up. Really need to reflect on what best we can do… and how to get some momentum in the PowerPlay,” Pandya said.

Suryakumar, batting at number ‌three, is not firing on all cylinders while Varma’s ​failures have put more pressure on the batting unit.

Pandya could look at moving ⁠Naman Dhir up the batting order to inject intent ⁠early, while England all-rounder Will Jacks may offer better balance in place of ‌Mitchell Santner.

Mumbai next faces Punjab Kings on Thursday, while third-placed RCB meets Lucknow Super ​Giants on Wednesday. 

Published on Apr 13, 2026

#IPL #lot #rethink #Hardik #Pandya #suffers #consecutive #defeat"> IPL 2026: ‘A lot of things need a rethink,’ says Hardik Pandya after MI suffers third consecutive defeat  Mumbai Indians needs a major rethink after suffering a third consecutive defeat in ​the Indian Premier League (IPL) on Sunday, said captain ‌Hardik Pandya.Mumbai lost to Royal Challengers Bengaluru ​by 18 runs at the Wankhede ⁠Stadium, leaving the five-time champion eighth in the 10-team table with just two points from four matches.Despite ‌boasting several Twenty20 World Cup-winning players—including Pandya, Suryakumar Yadav, Jasprit Bumrah ‌and Tilak Varma—Mumbai has struggled to ‌generate ⁠any momentum.ALSO READ |        Bumrah’s wicket-less run an unpleasant confrontation for MI“A lot of things need ⁠a rethink. But we have to see other options we can have, with the bat and the ball,” Pandya ​said at the ‌post-match presentation.“We need to still bat and bowl well. If you do that, irrespective of the toss (we should be fine).”Mumbai’s struggles have been ‌most evident in the PowerPlay.The lack ​of early wickets and limited support for Bumrah has raised concerns about the ⁠bowling attack, with opponents able to see off the India pacer before targeting the rest.“Last couple ‌of games, as a bowling and batting unit, we have been catching up. Really need to reflect on what best we can do… and how to get some momentum in the PowerPlay,” Pandya said.Suryakumar, batting at number ‌three, is not firing on all cylinders while Varma’s ​failures have put more pressure on the batting unit.Pandya could look at moving ⁠Naman Dhir up the batting order to inject intent ⁠early, while England all-rounder Will Jacks may offer better balance in place of ‌Mitchell Santner.Mumbai next faces Punjab Kings on Thursday, while third-placed RCB meets Lucknow Super ​Giants on Wednesday. Published on Apr 13, 2026  #IPL #lot #rethink #Hardik #Pandya #suffers #consecutive #defeat
Sports news

Bumrah’s wicket-less run an unpleasant confrontation for MI

“A lot of things need ⁠a rethink. But we have to see other options we can have, with the bat and the ball,” Pandya ​said at the ‌post-match presentation.

“We need to still bat and bowl well. If you do that, irrespective of the toss (we should be fine).”

Mumbai’s struggles have been ‌most evident in the PowerPlay.

The lack ​of early wickets and limited support for Bumrah has raised concerns about the ⁠bowling attack, with opponents able to see off the India pacer before targeting the rest.

“Last couple ‌of games, as a bowling and batting unit, we have been catching up. Really need to reflect on what best we can do… and how to get some momentum in the PowerPlay,” Pandya said.

Suryakumar, batting at number ‌three, is not firing on all cylinders while Varma’s ​failures have put more pressure on the batting unit.

Pandya could look at moving ⁠Naman Dhir up the batting order to inject intent ⁠early, while England all-rounder Will Jacks may offer better balance in place of ‌Mitchell Santner.

Mumbai next faces Punjab Kings on Thursday, while third-placed RCB meets Lucknow Super ​Giants on Wednesday. 

Published on Apr 13, 2026

#IPL #lot #rethink #Hardik #Pandya #suffers #consecutive #defeat">IPL 2026: ‘A lot of things need a rethink,’ says Hardik Pandya after MI suffers third consecutive defeat

Mumbai Indians needs a major rethink after suffering a third consecutive defeat in ​the Indian Premier League (IPL) on Sunday, said captain ‌Hardik Pandya.

Mumbai lost to Royal Challengers Bengaluru ​by 18 runs at the Wankhede ⁠Stadium, leaving the five-time champion eighth in the 10-team table with just two points from four matches.

Despite ‌boasting several Twenty20 World Cup-winning players—including Pandya, Suryakumar Yadav, Jasprit Bumrah ‌and Tilak Varma—Mumbai has struggled to ‌generate ⁠any momentum.

ALSO READ | Bumrah’s wicket-less run an unpleasant confrontation for MI

“A lot of things need ⁠a rethink. But we have to see other options we can have, with the bat and the ball,” Pandya ​said at the ‌post-match presentation.

“We need to still bat and bowl well. If you do that, irrespective of the toss (we should be fine).”

Mumbai’s struggles have been ‌most evident in the PowerPlay.

The lack ​of early wickets and limited support for Bumrah has raised concerns about the ⁠bowling attack, with opponents able to see off the India pacer before targeting the rest.

“Last couple ‌of games, as a bowling and batting unit, we have been catching up. Really need to reflect on what best we can do… and how to get some momentum in the PowerPlay,” Pandya said.

Suryakumar, batting at number ‌three, is not firing on all cylinders while Varma’s ​failures have put more pressure on the batting unit.

Pandya could look at moving ⁠Naman Dhir up the batting order to inject intent ⁠early, while England all-rounder Will Jacks may offer better balance in place of ‌Mitchell Santner.

Mumbai next faces Punjab Kings on Thursday, while third-placed RCB meets Lucknow Super ​Giants on Wednesday. 

Published on Apr 13, 2026

#IPL #lot #rethink #Hardik #Pandya #suffers #consecutive #defeat

Mumbai Indians needs a major rethink after suffering a third consecutive defeat in ​the Indian…

Batters fire Royal Challengers Bengaluru past Mumbai Indians in high-scoring contest

“Yes, that was the toughest part for me. Every time Rasikh bowls, he takes five minutes,” Rutherford said.

“As a batter, you need momentum. Every time you have momentum, when there is a stop and start, it just keeps slowing up the game. It’s something that no one can control. You just have to learn from it. Hopefully, next time, you just try and stay in the game or try some way of being ahead of the game.”

With temperatures expected to rise further and an extreme heatwave forecast for the Maximum City later this week, prolonged T20 contests could become a recurring theme when MI hosts Punjab Kings on Thursday.

Another contributing factor is the IPL’s revised slow over-rate regulations. Until 2024, captains faced match bans — along with heavy fines — after three offences.

Since the 2025 season, however, the IPL governing council has introduced a demerit points system, with suspensions a distant possibility over a 36-month period. The shift appears to have reduced the urgency among captains to maintain over-rates, further slowing down the game.

It is perhaps time to remind everyone involved in the IPL that T20 cricket is supposed to be fast-paced in terms of speed of the game, not just the run-rate. Is anybody listening?

Published on Apr 13, 2026

#IPL #Prolonged #interruptions #slow #overrate #RCB #pose #threats #purpose #T20s"> IPL 2026: Prolonged interruptions, slow over-rate in MI vs RCB pose threats to the very purpose of T20s  If the Royal Challengers Bengaluru’s innings — which stretched more than half an hour beyond the prescribed 90 minutes in the Indian Premier League (IPL) — was an example of cricket’s quickest format moving at a snail’s pace, the worst was yet to follow at the Wankhede Stadium on Sunday night.After a 16-minute innings break, the Mumbai Indians’ (MI) chase lasted 124 minutes.The match eventually wrapped up nine minutes shy of midnight, taking the total duration to four hours and 21 minutes. It was long enough to set social media abuzz, with fans debating whether the marquee clash had outlasted several Indian films — not just Lagaan but even Dhurandhar.To be fair, Mumbai experienced perhaps its hottest day of the summer so far, with players battling dehydration and requiring frequent medical attention. The match also featured 11 reviews and at least five injury-related stoppages, each contributing to the sluggish pace.Yet, such prolonged interruptions defeat the very purpose of T20 cricket and test the concentration of players at the crease.Sherfane Rutherford, whose lone fightback helped MI reduce the margin of defeat, admitted that maintaining focus amid repeated stoppages proved challenging.Rutherford waited patiently as Rasikh Salam went down thrice in the 18th over before eventually heading back to the pavilion after the fifth ball — an over that epitomised the stop-start nature of the contest.ALSO READ | Batters fire Royal Challengers Bengaluru past Mumbai Indians in high-scoring contest“Yes, that was the toughest part for me. Every time Rasikh bowls, he takes five minutes,” Rutherford said.“As a batter, you need momentum. Every time you have momentum, when there is a stop and start, it just keeps slowing up the game. It’s something that no one can control. You just have to learn from it. Hopefully, next time, you just try and stay in the game or try some way of being ahead of the game.”With temperatures expected to rise further and an extreme heatwave forecast for the Maximum City later this week, prolonged T20 contests could become a recurring theme when MI hosts Punjab Kings on Thursday.Another contributing factor is the IPL’s revised slow over-rate regulations. Until 2024, captains faced match bans — along with heavy fines — after three offences.Since the 2025 season, however, the IPL governing council has introduced a demerit points system, with suspensions a distant possibility over a 36-month period. The shift appears to have reduced the urgency among captains to maintain over-rates, further slowing down the game.It is perhaps time to remind everyone involved in the IPL that T20 cricket is supposed to be fast-paced in terms of speed of the game, not just the run-rate. Is anybody listening?Published on Apr 13, 2026  #IPL #Prolonged #interruptions #slow #overrate #RCB #pose #threats #purpose #T20s
Sports news

Batters fire Royal Challengers Bengaluru past Mumbai Indians in high-scoring contest

“Yes, that was the toughest part for me. Every time Rasikh bowls, he takes five minutes,” Rutherford said.

“As a batter, you need momentum. Every time you have momentum, when there is a stop and start, it just keeps slowing up the game. It’s something that no one can control. You just have to learn from it. Hopefully, next time, you just try and stay in the game or try some way of being ahead of the game.”

With temperatures expected to rise further and an extreme heatwave forecast for the Maximum City later this week, prolonged T20 contests could become a recurring theme when MI hosts Punjab Kings on Thursday.

Another contributing factor is the IPL’s revised slow over-rate regulations. Until 2024, captains faced match bans — along with heavy fines — after three offences.

Since the 2025 season, however, the IPL governing council has introduced a demerit points system, with suspensions a distant possibility over a 36-month period. The shift appears to have reduced the urgency among captains to maintain over-rates, further slowing down the game.

It is perhaps time to remind everyone involved in the IPL that T20 cricket is supposed to be fast-paced in terms of speed of the game, not just the run-rate. Is anybody listening?

Published on Apr 13, 2026

#IPL #Prolonged #interruptions #slow #overrate #RCB #pose #threats #purpose #T20s">IPL 2026: Prolonged interruptions, slow over-rate in MI vs RCB pose threats to the very purpose of T20s

If the Royal Challengers Bengaluru’s innings — which stretched more than half an hour beyond the prescribed 90 minutes in the Indian Premier League (IPL) — was an example of cricket’s quickest format moving at a snail’s pace, the worst was yet to follow at the Wankhede Stadium on Sunday night.

After a 16-minute innings break, the Mumbai Indians’ (MI) chase lasted 124 minutes.

The match eventually wrapped up nine minutes shy of midnight, taking the total duration to four hours and 21 minutes. It was long enough to set social media abuzz, with fans debating whether the marquee clash had outlasted several Indian films — not just Lagaan but even Dhurandhar.

To be fair, Mumbai experienced perhaps its hottest day of the summer so far, with players battling dehydration and requiring frequent medical attention. The match also featured 11 reviews and at least five injury-related stoppages, each contributing to the sluggish pace.

Yet, such prolonged interruptions defeat the very purpose of T20 cricket and test the concentration of players at the crease.

Sherfane Rutherford, whose lone fightback helped MI reduce the margin of defeat, admitted that maintaining focus amid repeated stoppages proved challenging.

Rutherford waited patiently as Rasikh Salam went down thrice in the 18th over before eventually heading back to the pavilion after the fifth ball — an over that epitomised the stop-start nature of the contest.

ALSO READ | Batters fire Royal Challengers Bengaluru past Mumbai Indians in high-scoring contest

“Yes, that was the toughest part for me. Every time Rasikh bowls, he takes five minutes,” Rutherford said.

“As a batter, you need momentum. Every time you have momentum, when there is a stop and start, it just keeps slowing up the game. It’s something that no one can control. You just have to learn from it. Hopefully, next time, you just try and stay in the game or try some way of being ahead of the game.”

With temperatures expected to rise further and an extreme heatwave forecast for the Maximum City later this week, prolonged T20 contests could become a recurring theme when MI hosts Punjab Kings on Thursday.

Another contributing factor is the IPL’s revised slow over-rate regulations. Until 2024, captains faced match bans — along with heavy fines — after three offences.

Since the 2025 season, however, the IPL governing council has introduced a demerit points system, with suspensions a distant possibility over a 36-month period. The shift appears to have reduced the urgency among captains to maintain over-rates, further slowing down the game.

It is perhaps time to remind everyone involved in the IPL that T20 cricket is supposed to be fast-paced in terms of speed of the game, not just the run-rate. Is anybody listening?

Published on Apr 13, 2026

#IPL #Prolonged #interruptions #slow #overrate #RCB #pose #threats #purpose #T20s

If the Royal Challengers Bengaluru’s innings — which stretched more than half an hour beyond…

Sunrisers Hyderabad takes on Rajasthan Royals in battle of explosive opening pairs

But Salt truly came into his elements against the spin duo of Mitchell Santner and Mayank Markande. Salt welcomed Santner in the fourth over with three clean hits over the fence followed by a boundary. Once the PowerPlay ended, Markande, the leg-spinner, was taken to task with three crisp fours and a towering six, as Salt’s assault gathered pace.

Shardul Thakur’s golden arm broke the 120-run partnership in the 11th over, but captain Patidar arrived with purpose. From the moment he tonked his first ball over mid-off for four, Patidar was precise and powerful, keeping the momentum intact.

Jasprit Bumrah’s probing spell — despite going wicketless for the fourth consecutive game — applied the brakes as RCB had to settle for 53 runs in the last five overs. The damage up front, however, was enough for RCB to return to winning ways.

Published on Apr 12, 2026

#RCB #IPL #Batters #fire #Royal #Challengers #Bengaluru #Mumbai #Indians #highscoring #contest"> MI vs RCB IPL 2026: Batters fire Royal Challengers Bengaluru past Mumbai Indians in high-scoring contest  Phil Salt was sensational in the first half — and not just in the PowerPlay. Rajat Patidar was potent with his power-hitting in the middle overs. And Tim David was devastating at the death.The trio’s exploits not only helped Royal Challengers Bengaluru pile on a gargantuan total but also take the chase out of the equation against the five-time champion Mumbai Indians’s reach to marquee Indian Premier League clash at the Wankhede Stadium.Riding on a whirlwind batting display through the innings — despite Virat Kohli’s relatively measured 38-ball 50 — RCB lived up to its billing as defending champion to post 240 for four, the second-highest total of the season.Once veteran Rohit Sharma had to retire hurt due to a hamstring issue after five overs into the chase, MI wilted under pressure against an accurate bowling attack. Krunal Pandya’s uncanny left-arm spin stifled the MI.Had it not been for Sherfane Rutherford’s impact as a sub in a lost cause, the margin of defeat – and the net run rate damage as a result – would have been much higher than 18 runs.While Rohit didn’t return to bat, Kohli also remained off the field for the second half after hurting his ankle during an anchor-like innings.Despite Kohli’s knock, RCB was too hot to handle in the first innings. While David finished with a towering six off Trent Boult over deep midwicket, Salt had begun in similar fashion against the Kiwi pacer.ALSO READ:Sunrisers Hyderabad takes on Rajasthan Royals in battle of explosive opening pairsBut Salt truly came into his elements against the spin duo of Mitchell Santner and Mayank Markande. Salt welcomed Santner in the fourth over with three clean hits over the fence followed by a boundary. Once the PowerPlay ended, Markande, the leg-spinner, was taken to task with three crisp fours and a towering six, as Salt’s assault gathered pace.Shardul Thakur’s golden arm broke the 120-run partnership in the 11th over, but captain Patidar arrived with purpose. From the moment he tonked his first ball over mid-off for four, Patidar was precise and powerful, keeping the momentum intact.Jasprit Bumrah’s probing spell — despite going wicketless for the fourth consecutive game — applied the brakes as RCB had to settle for 53 runs in the last five overs. The damage up front, however, was enough for RCB to return to winning ways.Published on Apr 12, 2026  #RCB #IPL #Batters #fire #Royal #Challengers #Bengaluru #Mumbai #Indians #highscoring #contest
Sports news

Sunrisers Hyderabad takes on Rajasthan Royals in battle of explosive opening pairs

But Salt truly came into his elements against the spin duo of Mitchell Santner and Mayank Markande. Salt welcomed Santner in the fourth over with three clean hits over the fence followed by a boundary. Once the PowerPlay ended, Markande, the leg-spinner, was taken to task with three crisp fours and a towering six, as Salt’s assault gathered pace.

Shardul Thakur’s golden arm broke the 120-run partnership in the 11th over, but captain Patidar arrived with purpose. From the moment he tonked his first ball over mid-off for four, Patidar was precise and powerful, keeping the momentum intact.

Jasprit Bumrah’s probing spell — despite going wicketless for the fourth consecutive game — applied the brakes as RCB had to settle for 53 runs in the last five overs. The damage up front, however, was enough for RCB to return to winning ways.

Published on Apr 12, 2026

#RCB #IPL #Batters #fire #Royal #Challengers #Bengaluru #Mumbai #Indians #highscoring #contest">MI vs RCB IPL 2026: Batters fire Royal Challengers Bengaluru past Mumbai Indians in high-scoring contest

Phil Salt was sensational in the first half — and not just in the PowerPlay. Rajat Patidar was potent with his power-hitting in the middle overs. And Tim David was devastating at the death.

The trio’s exploits not only helped Royal Challengers Bengaluru pile on a gargantuan total but also take the chase out of the equation against the five-time champion Mumbai Indians’s reach to marquee Indian Premier League clash at the Wankhede Stadium.

Riding on a whirlwind batting display through the innings — despite Virat Kohli’s relatively measured 38-ball 50 — RCB lived up to its billing as defending champion to post 240 for four, the second-highest total of the season.

Once veteran Rohit Sharma had to retire hurt due to a hamstring issue after five overs into the chase, MI wilted under pressure against an accurate bowling attack. Krunal Pandya’s uncanny left-arm spin stifled the MI.

Had it not been for Sherfane Rutherford’s impact as a sub in a lost cause, the margin of defeat – and the net run rate damage as a result – would have been much higher than 18 runs.

While Rohit didn’t return to bat, Kohli also remained off the field for the second half after hurting his ankle during an anchor-like innings.

Despite Kohli’s knock, RCB was too hot to handle in the first innings. While David finished with a towering six off Trent Boult over deep midwicket, Salt had begun in similar fashion against the Kiwi pacer.

ALSO READ:Sunrisers Hyderabad takes on Rajasthan Royals in battle of explosive opening pairs

But Salt truly came into his elements against the spin duo of Mitchell Santner and Mayank Markande. Salt welcomed Santner in the fourth over with three clean hits over the fence followed by a boundary. Once the PowerPlay ended, Markande, the leg-spinner, was taken to task with three crisp fours and a towering six, as Salt’s assault gathered pace.

Shardul Thakur’s golden arm broke the 120-run partnership in the 11th over, but captain Patidar arrived with purpose. From the moment he tonked his first ball over mid-off for four, Patidar was precise and powerful, keeping the momentum intact.

Jasprit Bumrah’s probing spell — despite going wicketless for the fourth consecutive game — applied the brakes as RCB had to settle for 53 runs in the last five overs. The damage up front, however, was enough for RCB to return to winning ways.

Published on Apr 12, 2026

#RCB #IPL #Batters #fire #Royal #Challengers #Bengaluru #Mumbai #Indians #highscoring #contest

Phil Salt was sensational in the first half — and not just in the PowerPlay.…