Raheja Developers
Indian real estate development company

Raheja Developers Limited, (RDL), formerly Raheja Developers Private Limited, is an insolvent Indian real estate development company with its headquarters in Delhi, India.
RDL was incorporated in 1990 by Navin Raheja, who currently serves as chairman.
Currently, the company is under insolvency proceedings as the Principal Bench of the National Company Law Tribunal (NCLT) has stated the initiation of insolvency proceedings against the realty firm over default on non-delivery of its Gurugram-based Shilas project. This order came on 19 November 2024. NCLT had also appointed an Interim Resolution Professional (IRP), suspending the board of the realty firm and putting it under the protection of moratorium against lenders, as per the provisions of the Insolvency & Bankruptcy Code.
History
Raheja Developers Limited was incorporated by Navin Raheja in 1990. The group has worked with contractors such as Aedas, Shapoorji-Pallonji and two of its joint-development projects were in collaboration with Tata Group. It had also collaborated with Dubai-based Arabtec Construction.
In 2008, Raheja Developers planned to build a Special Enterprise Zone (SEZ) in Gurgaon at an estimated cost of $660M US. The development was to be on a 255-acre (103 ha) site, but the project did not advance. The Government of India announced denotification of the SEZ project on 29 January 2014.
Begin with the source’s own compact description: “Raheja Developers” is indian real estate development company. The dossier treats that line as a proposition to test through Raheja, Developers and Indian, not as a finished interpretation.
Why this record matters
The phrase “indian real estate development company” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Maps, plans, fabric surveys and administrative records can establish how the site’s name, extent and function changed over time. The source revision retrieved here is dated Aug 25, 2026. The linked authority identifier is Q17085318. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1990, 2024, 2008 and 2014.
Modern boundaries and familiar names can conceal earlier jurisdictions or structures that do not align with the present site. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Raheja Developers”, its source revision and the description used here.
- Expand the search: follow Raheja Developers primary sources, Raheja Developers archive and Raheja research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Raheja Developers”?
- What physical evidence or contemporary plan supports the description?
- Which authority defined the place, boundary or structure at the relevant date?
Search terms from this dossier
This entry incorporates text from “Raheja Developers” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.