Ro-Ko Season at Wankhede as Rohit and Kohli Set for MI vs RCB Fireworks

It’s Ro-Ko season in the IPL, and while the broadcast hype hasn’t quite turned it into a full-blown spectacle yet, the setup for the next meeting is tailor-made for fireworks. On Sunday night at the Wankhede Stadium, Mumbai Indians and Royal Challengers Bengaluru will line up against each other with Rohit Sharma and Virat Kohli—the sport’s most bankable rivalry in the franchise era—taking centre stage. MI versus RCB always carries its own brand of excitement, even if it isn’t typically labelled as the season’s “main event” the way Mumbai’s clashes with Chennai Super Kings often are. Still, the fresh Ro-Ko storyline adds spice to an already electric matchup, especially because both teams arrive after heavy defeats at the hands of Rajasthan Royals in their most recent outings, a run powered by Vaibhav Sooryavanshi for the visitors.

Rohit, who will turn 39 later this month, and Kohli, aged 37, may not have set the stadiums alight with the kind of sustained, breathtaking dominance seen at their peak, but they have provided solid foundations early in the campaign. So far, both have been striking in the 168 to 180 range, and each has managed a fifty in the three matches their respective teams have played. Rohit, even if only briefly, found himself in the mix for the Orange Cap. Even in the autumn of their careers, they continue to tilt games simply by making the right starts and keeping their teams in the chase of big totals—or in the fight while defending. The early overs, as ever, will determine how much control the batting side can seize.

Kieron Pollard, however, tried to shift the focus away from individual star power. “As you said, it’s the Rohit-Kohli show. I look at it as Mumbai Indians versus Royal Challengers Bengaluru, and let the individuals enjoy this phase of their careers,” the MI batting coach said, underscoring that a team sport can’t be reduced to two names on the marquee. Yet in this specific clash, one player is hard to ignore because of the way his form has dipped: Jasprit Bumrah. The MI spearhead has been wicketless so far this season, and the drought has stretched further—he is yet to take a wicket in his last four IPL matches, including Qualifier 2 of the 2025 season. Questions have naturally started swirling around workload and whether fatigue could be a factor. In the most recent game in Guwahati, he looked uncharacteristically slow, working in the 130s with his pace.

Despite the concerns around rhythm and pace, the MI batting coach sounded calm when asked about Bumrah’s situation. “It can be 97, it can be 105. From our side, it’s fine. We don’t look at cricket that way, and I, as an individual, never look at it like that. Cricket is a team sport. For us, it’s about coming together as one and trying to get the desired result at the end of the day. Otherwise, you start looking into different things and creating narratives that aren’t really there. For us, he’s fine—he’s fit, he’s firing. And for your sake, I hope he gets five wickets tomorrow,” he said, effectively insisting that the squad will trust Bumrah’s process even if the wickets haven’t arrived yet.

The fixture is important for both sides, but it carries extra weight for the home team. MI ended a 13-year hoodoo of losing their opening matches, only to squander the advantage by dropping the next two games. They now need to make the most of familiar home conditions—an area where RCB have also shown they can be effective so far in the tournament. At the Wankhede, though, conditions tend to turn even “small” advantages into large ones, and this encounter looks built for batting dominance. When: MI vs RCB, IPL 2026, April 12 at 7:30 PM IST. Where: Wankhede Stadium, Mumbai. What to expect: A compact ground, a placid surface, and batting-heavy lineups are the recipe here, with the expectation that totals above 200 are well within reach. In fact, the last two T20 matches at the venue saw a chase of 220 successfully completed, while even a score of 250 looked vulnerable to being chased down.

On head-to-head numbers, MI hold the edge: MI 19–15 RCB. The trend at the Wankhede is even more telling, with Mumbai winning six of their last seven meetings against RCB at the venue, and the visitors’ only win in that stretch arriving last year. With that history behind them, MI will want to convert their home advantage into points, while RCB will aim to strike early and avoid another game where the momentum slips away.

Team Watch

Mumbai Indians

Injuries/Unavailabilities: Will Jacks has not yet reported, but Kieron Pollard has confirmed that Mitchell Santner—who missed the previous match—is available. If Santner comes into the XI, then one of Allah Ghazanfar or Trent Boult is expected to make way.

Tactics & Match-ups: Devdutt Padikkal and Tim David have been the main danger men for RCB, and it would not be surprising if MI manage Bumrah’s overs with those two batters in mind. Bumrah’s matchup has traditionally been favourable against Padikkal. Pollard also indicated MI’s intent to keep Tim David under control, noting that David spent three seasons with Mumbai and that the franchise will be wary of his ability to change the tempo when the ball is in the right areas.

Probable XII: Rohit Sharma, Ryan Rickelton (wk), Tilak Varma, Suryakumar Yadav, Hardik Pandya (c), Naman Dhir, Sherfane Rutherford, Mitchell Santner, Shardul Thakur, Deepak Chahar, Trent Boult, Jasprit Bumrah.

Royal Challengers Bengaluru

Injuries/Unavailabilities: After travelling from Guwahati to Mumbai on Saturday, RCB opted to rest rather than train. There has been no update suggesting any injury to their players, with the expectation that everyone will be available for selection.

Tactics & Match-ups: Jacob Bethell is a probable option in place of Phil Salt, though that switch would still be a tough call given Salt’s impact after performing strongly against CSK in the second match. Suyash Sharma could be recalled as an Impact Player, unless RCB decide against it, particularly if they fear a repeat of the kind of collapse witnessed in Guwahati—when the team had to bring in Venkatesh Iyer as the Impact Player. Abhinandan Singh is also likely to be discussed by the management as they finalize their balance for Mumbai’s conditions.

Probable XII: Virat Kohli, Phil Salt/Jacob Bethell, Devdutt Padikkal, Rajat Patidar (c), Jitesh Sharma (wk), Tim David, Romario Shepherd, Krunal Pandya, Bhuvneshwar Kumar, Abhinandan Singh, Josh Hazlewood, Suyash Sharma.

Did you know Jasprit Bumrah has not picked a wicket in his last four IPL games, a run that goes back to the second Qualifier from last season. It has been 98 balls since his most recent wicket in the competition, marking the second-longest wicketless streak of his IPL career. Another recent Wankhede trend: Venkatesh Iyer has won the Player of the Match award in two of his last three appearances at the venue. RCB’s Guwahati loss on Friday also carried a notable statistic, being their first defeat in a designated away league fixture in 11 games since 2024.

What they said

On Rohit Sharma completing 15 years with MI, Kieron Pollard said: “It’s a great honour, a privilege, and an achievement for any individual to be with one franchise for that long. Not many can say that. Fortunately, I can, but Rohit has been a great leader for us over the years. He’s also been a terrific leader for Indian cricket. He’s a legend in his own right, and as I said, long may that continue. We will continue to celebrate his success, and I’m certainly happy to have him in our dressing room.”

RCB’s Bhuvneshwar Kumar, speaking about the decision-making around Phil Salt and Jacob Bethell, added: “I think it started from last year. Phil Salt did well for us. I know the way Jacob Bethell batted in the World Cup, there is always a temptation to include him. But as a team, we have tried to keep things as simple as possible. I understand that things may look different from the outside, but internally we know he is a very good player. At the same time, this is largely the same squad that did well last season, and everyone is performing. So I don’t think there was much we needed to change.”