The projects, the people building them, and the infrastructure behind the headlines. Explore what is documented—and what still needs evidence.
Dataset refreshed 28 Oct 2026 · 18 canonical published records · not a census of every development.
Tracked projects
18
Distinct developers
7
Projects with reviewed fields
8
Neopolis records
2
One explicit scope. No corridor inflation.
Includes only published Hyderabad records whose canonical locality is exactly Kokapet or Neopolis, counted once by project ID. Neopolis is shown separately on each card. Narsingi, Financial District, mixed Kokapet/Narsingi labels and nearby-road labels are not included. This is a dataset classification, not a surveyed land boundary.
Know the area
The place. The projects. The evidence.
Use the locality names recorded on each project to orient your research. This view includes Kokapet and Neopolis without silently adding neighbouring Narsingi or Financial District projects.
Neopolis records remain identifiable in the explorer. Exact station catchments, travel times, civic service coverage and surveyed boundaries are not established here.
The records below provide planning context, not a fresh change alert. Checking a source today does not mean a development happened today. Older imports, stale checks and unresolved evidence are excluded from fresh updates.
How updates qualify
A reviewed, material, non-superseded event needs a specific date within 30 days and a current successful source check. Historical imports, duplicate events, inaccessible sources and dates that are unknown or in the future do not qualify. Project updates use the existing material-change evidence rules and an exact project match. Phase-specific changes without a reviewed phase association remain withheld. This is not a notification service.
Infrastructure, without the hype
Planning is not completion.
Read what the issuing agency actually says. Proposed, approved, under-construction and completed are different stages; only stages supported by the linked record are shown.
ProposedPublication date not recorded
A proposed metro corridor to Kokapet Neopolis
HMRL’s Phase-II overview includes an 11.6 km proposed corridor between Raidurg and Kokapet Neopolis. The page does not establish an operating service or a confirmed opening date.
Why it matters · scope & limitations
Useful transport-planning context when comparing locations. It is not proof of construction, final approval, a station location or a benefit to a particular project.
Scope: Raidurg–Kokapet Neopolis corridor. An agency publication is not independent authentication of every underlying permission.
Hyderabad Metro Rail Limited · Official agency publication
The dated agency update records coordination with stakeholder departments to progress no-objection certificates. It does not establish a construction start or completion.
Why it matters · scope & limitations
Shows a documented step in the wider planning process. This programme-level record is not permission for an individual building or evidence that the Kokapet corridor is complete.
Scope: Phase-II programme. An agency publication is not independent authentication of every underlying permission.
Hyderabad Metro Rail Limited · Official agency publication
2 of 18 tracked projects have a matching reviewed RERA identifier; 0 have conflicting identifier evidence. An identifier alone does not establish registration validity, legal clearance or approval of every phase.
The reviewed locality sources do not establish final metro commissioning, exact station locations, or a complete road and utility delivery schedule. Individual project completion and permissions need their own phase-specific records.
How do we know?
A check is not a change.
2 of 4 locality references have a current reviewed check. Availability is reported per source; unchecked details remain unknown. Reference links and short factual summaries are used, not republished document copies.
Phase-II corridor overview
Proposed Raidurg–Kokapet Neopolis corridor
Hyderabad Metro Rail Limited · Official agency publication
Published: Publication date not recorded. Review interval: 30 days. Reference-only use; bulk ingestion and document republication are not approved. A failed check is not a negative finding about the locality.
Phase-II clearance coordination
Phase-II programme; not an individual project approval
Hyderabad Metro Rail Limited · Official agency publication
Published: 18 Aug 2026. Review interval: 30 days. Reference-only use; bulk ingestion and document republication are not approved. A failed check is not a negative finding about the locality.
Kokapet area reference
Kokapet area context; not an individual project approval
Hyderabad Metropolitan Development Authority · Official agency publication
Published: Publication date not recorded. Review interval: 30 days. Reference-only use; bulk ingestion and document republication are not approved. A failed check is not a negative finding about the locality.
Neopolis layout reference
Named Neopolis layout document; phase details not reviewed
Hyderabad Metropolitan Development Authority · Official agency publication
Published: Publication date not recorded. Review interval: 30 days. Reference-only use; bulk ingestion and document republication are not approved. A failed check is not a negative finding about the locality.
Recorded project categories
All 18 records. These are catalog categories, not verified project specifications. Select a bar to filter the explorer.
Recorded construction status
All 18 records. "Ready to move" does not establish OC, legal completion or delivery of every phase.
1.74 acresDeveloper-reported specification · checked 9 Oct 2026View field evidence
Towers
1 tower / single high-rise building with North and South wings around shared private-lobby/core planning.Developer-reported specification · checked 9 Oct 2026View field evidence
Reviewed means an existing accepted developer review matches the exact canonical field value and project. It does not verify the whole project or authenticate a government record. Chart denominator: 18 projects per field.
Project identity6/18 reviewed
12 pending · 0 conflict · 0 missing
Locality4/18 reviewed
14 pending · 0 conflict · 0 missing
Property category0/18 reviewed
18 pending · 0 conflict · 0 missing
Construction / delivery status0/18 reviewed
18 pending · 0 conflict · 0 missing
Configurations0/18 reviewed
18 pending · 0 conflict · 0 missing
Land area8/18 reviewed
8 pending · 0 conflict · 2 missing
Towers8/18 reviewed
9 pending · 0 conflict · 1 missing
Homes / units3/18 reviewed
12 pending · 1 conflict · 2 missing
Possession reference0/18 reviewed
13 pending · 0 conflict · 5 missing
RERA identifier2/18 reviewed
12 pending · 0 conflict · 4 missing
Price context
No misleading market median.
Price statistics are withheld. The current evidence does not establish a comparable cohort with reviewed price values, observation dates, matching configurations, area measurement and inclusions. Advertised prices are not registered transaction values; stale prices and commercial records cannot be mixed with current residential asking prices.
Use project-level references in Compare, or compare your own dated quotations with the all-in cost tool.
18 projects and 7 distinct linked developers are tracked in this scope. 8 projects have at least one qualifying reviewed field. Explore individual configurations and dates without treating them as a complete market sample.
A dominant configuration, delivery pipeline and infrastructure completion cannot be established from unsupported catalog text. These insights remain pending. No demand trend, appreciation, ROI or rental-yield forecast is inferred.