raees vs kaabil: shah rukh vs hrithik
Looks like Shah Rukh Khan’s late night visit to Hrithik Roshan’s residence did not work out. Kaabil’s director Sanjay Gupta announced on Twitter today (July 20) that the Hrithik Roshan starrer will release on January 26 next year, just as was originally planned.
The 50-year-old star, along with producer Ritesh Sidhwani, visited Hrithik Roshan’s home on the night of July 18.
The Dilwale star reportedly went to Hrithik’s house to convince him to shift the release date of Kaabil which is slated to release on Januray 26, next year.
Now, Shah Rukh Khan’s Raees was supposed to release on Eid this year. However, to avoid clash with Salman Khan’s Sultan, the makers of Raees, Excel Entertainment and Red Chilies Entertainment, pushed the release date to Republic Day in 2017, which is when Kaabil is slated to release.
Shah Rukh later tweeted on July 19 about the meeting, and nothing from the tweet hinted about anything unfortunate happening there
Earlier, during an interaction with the media during Eid, Shah Rukh said, “We have spoken to Hrithik and also Ritesh Sidhwani and Farhan Akhtar (producers of Raees). That was a month ago, but I guess now we can do some adjustments. Rakeshji (Rakesh Roshan, Kaabil’s producer) and Ritesh and Farhan will be meeting again. We are trying to figure things out, so we don’t have a clash.”
Elaborating on his reason for an exclusive release date, SRK added, “I think a big film should release in 3,500-4,000 theatres. When two big films release, we don’t get the magnitude of theatrical release we want. Till the time we don’t have 8,000-10,000 theatres, no two big films can come. Raees is nearly ready, we are only left to shoot that last shot.”
When Hrithik was asked about the same at the press conference of Mohenjo Daro, he said, “SRK and I are actors and this should be left to the producers to discuss.”
Well, by the looks of it, both Raees and Kaabil will inevitably clash in the Republic Day weekend next year, unless SRK decides to postpone Raees’s release yet again.