Royals push to stay in Jaipur despite venue challenges
A return to the Sawai Mansingh Stadium in Jaipur is looking increasingly likely for Rajasthan Royals, even as unresolved logistical concerns continue to cast a shadow over their IPL 2026 preparations. According to a report by cricbuzz, while the Board of Control for Cricket in India (BCCI) has yet to officially greenlight the venue, discussions are advancing in favor of retaining Jaipur as the primary home ground — if key conditions are met in time.
The franchise had earlier evaluated relocation possibilities, spurred by questions over the readiness of facilities at their traditional home base. But mounting pressure from the Rajasthan state government, which reportedly intervened to keep the Royals grounded in their namesake city, has shifted the focus back to fixing infrastructural gaps rather than abandoning the venue altogether.
Stadium readiness remains a key concern
Central to the delay is the stadium’s lack of full preparedness. The Royals’ management is understood to have insisted that core amenities and spectator facilities must be brought up to standard before the tournament kicks off. With the IPL 2026 season scheduled to begin on March 26, time is running short to execute upgrades. The franchise has maintained that it will only proceed in Jaipur if these expectations are fully addressed.
Should these requirements be met, the Royals are expected to host four of their seven home fixtures in Jaipur, with the remaining three matches taking place in Guwahati — an arrangement that has been in place since previous seasons.
Alternate venues considered as contingency
Amid the uncertainty, the Royals have held parallel talks with the Maharashtra Cricket Association (MCA) about the possibility of shifting games to Pune. According to a report by cricbuzz, these discussions have not yielded a concrete outcome, and the Pune option remains on standby as a fallback if Jaipur fails to meet the necessary standards.
As previously reported by cricbuzz, the Royals were among several franchises that reached out to explore Pune as a potential host. However, no formal shift was confirmed, with logistical and administrative hurdles slowing the process.
MI and RCB add to wider IPL venue complications
The Royals’ venue negotiations come at a time when other franchises are also navigating venue instability. Royal Challengers Bengaluru (RCB), facing doubts over the availability of Chinnaswamy Stadium, reportedly approached Mumbai Indians for temporary access to Navi Mumbai’s DY Patil Stadium. However, Mumbai Indians advised RCB to consider other cities first — including Indore, Raipur, Visakhapatnam, and Cuttack — before any arrangement in Mumbai could be entertained.
A similar response was extended to the Royals when they initially explored Mumbai as an emergency venue option. Despite these parallel inquiries, neither RCB nor RR has formalized a move outside their traditional bases.
Broader friction with state associations lingers
Complicating the Royals’ home base situation further is their recent strained relationship with the Rajasthan Cricket Association (RCA). Tensions flared in the previous IPL season following allegations and disagreements over issues ranging from complimentary ticket allocations to performance-related controversies. While no direct impact on this year’s venue decision has been confirmed, the history of discord may still be influencing the cautious pace of progress.
Final schedule pending BCCI announcement
As franchises await final confirmation of home venues, the BCCI has yet to release the official match schedule for IPL 2026. The announcement is expected only after the declaration of state assembly election dates in Tamil Nadu, Kerala, Puducherry, and West Bengal — developments that could further impact venue logistics across the league.
For Rajasthan Royals, the clock is ticking. Their preference remains a homecoming in Jaipur, but the final word will depend on whether stadium readiness can be guaranteed in time for the high-stakes tournament’s opening week.
