Method: how this register is built, scored and corrected

The Register Standing Score

Five criteria, 100 points. Every one is a public GujRERA field, and none of them is a judgement about a company. Where a criterion cannot be scored for a record, the points are removed from that record's basis rather than guessed, the score is expressed against the reduced basis, and the basis is printed beside the figure.

One structural bias is worth stating plainly, because it is visible in the results: criterion three rewards a declared completion date that has not yet arrived, so recently registered projects score higher than older ones on that criterion by construction. Read the score as a measure of filing record and registration evidence at this date. It is not a measure of build quality, of delivery, of price or of whether a project is a sound purchase.

How the 33 entries were found

Full Ahmedabad district registered-project list pulled from the GujRERA dashboard API (5,435 projects), then filtered for Dholera evidence. Cross-checked against 24 live global-search queries; the search union added zero Dholera projects the district list did not already contain.

Inclusion rule. A project is included only if its own GujRERA record carries Dholera evidence: taluka segment DHOLERA in the registration number, authority segment DSIRDA, approvingAuthority naming the Dholera Special Investment Region Development Authority, subDistName Dholera, a moje/village inside the DSIRDA boundary, or the literal string DHOLERA in the registered name or address. Every matched criterion is written into dholera_evidence.

The 22 village names inside the DSIRDA boundary, taken from the official DSIRDA village map, are: Gorasu, Panchi, Otariya, Mundi, Mingalpur, Bhimtalav, Cher, Dholera, Gogla, Bhangadh, Mahadevpura, Bhadiyad, Khun, Sodhi, Bavaliyari, Kadipur, Sangasar, Ambali, Hebatpur, Sandhida, Rahtalav, Zankhi.

Promoter identity: what is not merged

GujRERA publishes no promoter identifier, so this register groups on the exact promoter name string printed on each project record. Names that look related are held apart, because merging them would assert a corporate identity the public record does not establish. Five pairs in this set are affected, and the effect on the developer counts is real: were 7 OAK DEVELOPERS and 7 OAK DEVELOPERS PRIVATE LIMITED one entity, that name would hold five registrations rather than four and one.

A promoter who can evidence that two names are one legal person can have them merged. The route is the correction route below, and the merge is logged.

What this data does not contain

Ten gaps are declared in the dataset itself and reproduced here in full, because a register that hides its holes is worth less than one that prints them.

• project_area (totAreaOfLand) is null on the GujRERA record for 10 of 33 projects, all of them DSIRDA-era registrations. This is not a scrape failure: the GujRERA project page itself renders 'Project Land Area:- Sq Mtrs' with no number for these. The same records do carry totAreaOfLandLayout and totLandAreaForProjectUnderReg, emitted as separate fields rather than substituted in.
• village (moje) is null on the GujRERA record for many pre-2023 registrations
• GujRERA has no per-project HTML page with a stable path. The public record is an Angular single-page app; the deep link emitted in gujrera_detail_page_url ('#/project-preview?id=<base64 projectRegId>') was read out of the app bundle and verified in a live browser against project 11091 (7 OAK SMART CITY). It is not a documented government URL scheme and could change without notice; gujrera_detail_api_url is the stable machine-readable fallback.
• Per-project complaint DETAIL (allegation text, orders, hearing record) is behind login: complain/secure/getby-projectId/{id} returns {"Error":"Invalid Request"} without a session token. Only complaint number, status and dates are public, via projectAllApplications.
• The gujrera_detail_page_url deep link needs a FRESH page load. The Angular component reads ?id= only in its constructor, so changing the hash inside an already-open GujRERA tab will keep showing the previous project. Opening the link in a new tab, or a hard reload, resolves it correctly (verified on projects 11091 and 30155).
• 3 projects are included at dholera_evidence_tier=INFERRED: their GujRERA record cites a Dholera SIR town-planning scheme and a Dhandhuka taluka, but the record never says 'Dholera' and names no DSIRDA village. Treat them as unconfirmed.
• registration_date is the GujRERA approval date (approvedOn / Registration.approvalDate). GujRERA publishes no separate 'certificate issue date'.
• project_status on the registration record is promoter-declared at registration time ('New'/'Ongoing') and is NOT a live construction status. Live progress is in qpr_filings and in the per-block progress percentages on the portal page.
• The dataset covers Ahmedabad district only. Bhavnagar district (which borders Dholera SIR) was pulled in full (719 projects) and returned zero Dholera/DSIRDA matches.
• Projects that were never registered, or whose registration lapsed and was purged from the district dashboard, cannot appear. GujRERA publishes no 'lapsed/deregistered' public list keyed to district.

These notes are reproduced verbatim from the dataset, with one exception: a stray extraction artefact inside the word "record" in the fourth note has been corrected. Nothing else in them has been edited.

The stamp key

Status on this register is carried by the form of a stamp, solid against outlined against dashed, so the register survives greyscale printing, photocopying and every kind of colour blindness. Colour never carries a meaning on its own here. Four forms are used and each one encodes a real field.

• OfficialThe GujRERA record itself names Dholera, a DSIRDA village, or DSIRDA as the approving authority. 30 of 33 entries.
• InferredThe record cites a Dholera SIR town planning scheme in a Dhandhuka taluka address but never says Dholera. Treat as unconfirmed. 3 of 33 entries.
• Date aheadThe completion date declared at registration falls on or after 4 August 2026. 16 of 33 entries.
• Date elapsedThe declared completion date has passed. It is a statement about a date, not about a building. 17 of 33 entries.

Corrections

If a figure here differs from the GujRERA record, the GujRERA record is right and this register is wrong. Write to corrections@dholera-realestate.com with the RERA registration number and the field in question. A correction that can be verified against the government record is applied and published on the changes page with the date and what changed.

Three things will not change a rank: a request to be moved up, an offer to pay, and a request to be removed from a register of public records. Nothing on this site is for sale, including position on it.

Publishing and design notes

Published by Bhavik Sarkhedi, ORCID 0009-0005-8094-0688. Data is released under the Creative Commons Attribution 4.0 International (CC BY 4.0), so it can be reused with attribution. Source records belong to GujRERA. This site is independent of GujRERA, of DSIRDA and of every promoter named on it.

The site is typeset in Bitter for display, Source Sans 3 for body text and Anonymous Pro for every number, registration number and label. All three are under the SIL Open Font License 1.1 and are self hosted as woff2 latin subsets. No font is loaded from a content delivery network and no third party script runs on any page.

Four colours are authored and no fifth exists anywhere in the stylesheet: a near-white sheet, a near-black ink, one registry green and one muted neutral. The green is spent on four things only, the rule at the head of every page, the section numbers, the rank numerals and the verification links out to GujRERA, so a reader learns in one page that green on this site means rank or verified. Every other tone in the file is that same ink laid over the sheet at a stated transparency. There is no tinted panel, no gradient, no shadow and no photograph on any page.