Dholera Developer & Project Rankings

Edition 2026.08 · Method and rubric
Verified 4 August 2026

How the score is worked out, and what it cannot tell you

This page shows you exactly how every rank on this site was produced, so you can disagree with it on the arithmetic rather than on trust. Every figure was read from the Gujarat Real Estate Regulatory Authority public portal on 4 August 2026. Nothing was estimated.

The score is 100 points split across five things the government already publishes about a project. Below are the five, what each is worth, how the 33 projects were picked out of 5,435, the ten known holes in the data, and how to tell us we are wrong.

§01

The five things the score counts

Five criteria, 100 points between them. Every one is a field GujRERA publishes, and not one of them is an opinion about a company. If a criterion cannot be worked out for a particular project, its points are taken out of that project's total rather than guessed at, the score is expressed against the smaller total, and the smaller total is printed next to the number so you can see it happened.

  • Register Standing Score. A mark out of 100 that this site works out for every project from five things the government already publishes: whether the record names Dholera, how many quarterly reports were filed, whether the completion date declared at registration has passed, how many complaint entries are on the public ledger, and how many other projects the promoter has registered. It measures paperwork. It says nothing about build quality or about price.
The Register Standing Score, edition 2026.08
CriterionWhat it measuresWeightScaleDataset field
C1Registration evidenceWhether the project's own GujRERA record carries Dholera or DSIRDA evidence, or whether Dholera has to be inferred from a town planning scheme number.20OFFICIAL evidence on the record: 20
INFERRED from a TP scheme number only: 10
dholera_evidence_tier
C2Quarterly progress filing rateQuarters with a submission on the GujRERA quarterly progress report ledger, divided by quarters scheduled.3535 points multiplied by submissions divided by quarters scheduled: 35
Not scorable where no quarter has yet fallen due: 0
qpr_filings
C3Declared completion date standingWhether the completion date declared on the registration record still lies ahead of the edition date. It measures a date, not a building.20Declared date falls on or after 4 August 2026: 20
Declared date already elapsed on 4 August 2026: 0
declared_completion_date
C4Complaint entries on the public ledgerHow many complaint rows GujRERA publishes against the project. A complaint entry is a filing, not a finding, and its substance is not public.15No complaint entry: 15
One complaint entry: 8
Two or more complaint entries: 0
complaints
C5Promoter register depthOther GujRERA-registered projects published on this project's own promoter record.10Three or more other registrations: 10
One or two: 6
None published: 0
promoter_other_gujrera_projects
Total 100 points. Ties are broken by earliest GujRERA approval date. Computed 4 August 2026 against the register as read that day.

One bias in this score is built in and worth saying out loud, because you can see it in the results. The third criterion rewards a completion date that has not yet arrived, so a project registered last year almost always beats one registered in 2021 on that criterion, whatever either has actually built. Read the score for what it is: how a project's paperwork stands on this date. It is not a measure of build quality, of whether the project will finish, of price, or of whether buying there is a good idea. That argument is set out at length on what a high score here does not mean.

§02

How 33 projects were picked out of 5,435

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.

Sources read for edition 2026.08
Endpoint or documentWhat it suppliedRecords returnedAccessed
https://gujrera.gujarat.gov.in/dashboard/get-district-wise-projectlist/0/0/all/Ahmedabad/allGujRERA district-wise registered project list, Ahmedabad district, all cost categories / all FY / all types54352026-08-04
https://gujrera.gujarat.gov.in/dashboard/get-district-wise-projectlist/0/0/all/Bhavnagar/allSame list for Bhavnagar district, used to prove no Dholera projects sit outside Ahmedabad district7192026-08-04
https://gujrera.gujarat.gov.in/project_reg/public/global-searchGujRERA public global search, POST {"query":"<term>"}; 24 Dholera/DSIRDA/village terms run as a cross-check against the district listnot applicable2026-08-04
https://gujrera.gujarat.gov.in/project_reg/public/getproject-details/{projectRegId}Per-project official registration record: area, carpet area, units, village, taluka, dates, authoritynot applicable2026-08-04
https://gujrera.gujarat.gov.in/quarter/public/getprojectqtrs/{projectRegId}Per-project quarterly progress report (QPR) filing historynot applicable2026-08-04
https://gujrera.gujarat.gov.in/project_reg/public/projectAllApplications/{projectRegId}Per-project application ledger: registration, extensions, annual compliance, complaints, challansnot applicable2026-08-04
https://gujrera.gujarat.gov.in/project_reg/public/getprev-project-list/{projectRegId}Promoter's other GujRERA projects (promoter history)not applicable2026-08-04
dsirda_villages_map.pdf, page 1Official DSIRDA village map; supplied the 22-village DSIRDA boundary list used as inclusion evidencenot applicable2026-08-04
Every one of these is a public GujRERA endpoint or an official DSIRDA document. Nothing on this site is drawn from a news report, a broker listing or a marketing page.
§03

Why similar company names are not added together

GujRERA does not give each builder a company number, only a name typed onto each project record. So this site groups projects by the exact name string, letter for letter, and joins nothing up. Two names that look like the same firm are kept apart, because deciding they are one company would be a claim about corporate ownership that the public record does not make.

That choice changes the counts, so here is the effect in the open. If 7 OAK DEVELOPERS and 7 OAK DEVELOPERS PRIVATE LIMITED were treated as one company, that name would hold five registrations instead of four and one. A builder who can show that two names are the same legal entity can have them merged, using the correction route further down this page, and the merge is written into the changes log. All five pairs are set out, with what merging each one would change, on the similar names page.

§04

What this data does not contain

Ten gaps are recorded in the dataset itself and reprinted here word for word. A register that hides its holes is worth less than one that prints them, and every one of these limits how far you should push a conclusion.

  • 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.

§05

What the four stamps mean

Small stamps appear beside rows across this site. Each one is a shape as well as a label, solid against outlined against dashed, so the meaning survives a black and white printout, a photocopy and every kind of colour blindness. Colour never carries the meaning on its own. There are four, and each reports a real field on the government record.

  • 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.
§06

How to tell us we are wrong

If a figure here differs from the GujRERA record, the GujRERA record is right and this site is wrong. Write to corrections@dholera-realestate.com with the registration number and which field is off. Anything we can confirm against the government record gets fixed and written up on the changes page, with the date and what changed.

Three things will not move a rank: asking to be moved up, offering to pay, and asking to be taken off a list built from public records. Nothing on this site is for sale, including a position on it.

§07

Who publishes this, and how it is made

Published by Bhavik Sarkhedi, . 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.

Measured text contrast, WCAG 2.x relative luminance, sRGB
ElementPairRatioWCAG
Body textink #0D1512 on paper #F8F9F717.55:1AAA
Rank numerals and verified stampsaccent #0E6E4E on paper5.92:1AA
Table header labelsink on paper17.55:1AAA
Secondary metadatasupport #63706A on paper4.90:1AA
Knockout masthead typepaper on solid ink17.55:1AAA
Knockout stamp typepaper on solid accent5.92:1AA
Lowest pair used anywhere is 4.90 to 1, which clears WCAG AA. Body text runs at 17.55 to 1, which is well past AAA.