What the government record does not tell you
Every ranking site quietly decides what to do with an empty field. Most fill it in, average it out, or drop the row so the table looks complete. This one prints the emptiness, and this page collects all of it in one place so you can see the shape of what is missing before you read anything else here.
The single largest hole is village, or moje, empty on 16 of the 33 records. Below that, 10 further limitations are declared in the dataset itself and reprinted here word for word.
- GujRERA. The Gujarat Real Estate Regulatory Authority. It is the state government body that a builder has to register a housing or plotting project with before advertising or selling any part of it. Registration is a legal requirement, not a quality award.
- Quarterly progress report. Every registered project owes GujRERA a short update each quarter. The portal shows how many were due and how many were actually filed. It records paperwork, not construction.
Field by field, what is missing
Eight fields, counted across all 33 registrations. A blank is not a zero. A project with no published land area has a land area; the government simply does not publish it, and treating that as zero would drag it to the bottom of every ranking for a reason that has nothing to do with the project.
That is why every sortable table on this site sends rows with no published value to the bottom rather than counting them as nil, and why the blank appears in the cell rather than a dash that could be mistaken for a real figure.
| Field on the government record | Records with a value | Records left blank | How this site handles it |
|---|---|---|---|
| Total project land areaThe overall size of the scheme, in square metres. | 23 | 10 | Printed as blank |
| Village, or mojeThe revenue village the land sits in. | 17 | 16 | Printed as blank |
| Total carpet areaThe saleable floor area, in square metres. It is meaningful for built projects and close to meaningless for a plotting scheme. | 32 | 1 | Printed as blank |
| Land area under registrationThe part of the scheme covered by this registration, in square metres. | 33 | 0 | Complete |
| Declared unit countHow many plots, shops or flats the registration covers. | 33 | 0 | Complete |
| TalukaThe sub-district the land sits in. | 33 | 0 | Complete |
| Declared completion dateThe date the builder told the government the project would be finished. | 33 | 0 | Complete |
| Registration approval dateThe date GujRERA approved the registration. | 33 | 0 | Complete |
| Counted directly from the 33 registration records. Status: OFFICIAL for every count. No field is imputed anywhere on this site. | |||
Source: GujRERA per-project registration record · Read 4 August 2026 · Status: OFFICIAL
Why the land area is missing on ten records
Ten registrations carry no total project land area. They are all older registrations, and this is not a failure of our reading: the government field itself is null on those records. Each of the ten still publishes the land area under registration, which is the part of the scheme the registration covers, so no row on this site is left without any size at all.
The practical effect is that a comparison of total scheme size across all 33 projects cannot be made honestly. A comparison of registered land can, and that is the column every size ranking on this site uses. It is stated on the size ranking as well, because a limitation only helps if it appears where the number appears.
The 10 limitations declared in the dataset
These are printed exactly as they were written when the data was collected, including the technical ones. They cover what could not be reached, what the portal does not expose, and what a reader should not conclude from this data.
- 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.
Two are worth translating into plain words. The complaint detail, meaning what a complaint was actually about and how it was decided, sits behind a login and is not public, so this register can only count complaint entries and must not describe them. And the project status printed at registration is what the builder declared on the day, not a live construction status, so no page here treats it as progress.
What we would publish if the record allowed it
Price per square metre, because it is the first thing anyone wants and the one thing the public record never carries. Construction progress, because the portal holds block by block percentages that are not in this edition of the data. Delivery, because completion certificates would settle arguments that ranking tables cannot. And the substance of complaints, which is the difference between a filing and a finding.
None of the four is invented here to fill the space. If a column becomes available, the page gets built and the addition is logged on the changes page with the date. Until then, the honest answer to all four is that we do not know.
How this register is builtWho is missing from the registerWhat a high rank does not mean