What this page is
This is a symmetric record, not a shame-list. For each tracked project on the Yamuna Expressway corridor it states one thing plainly: the RERA-registered completion date on file, bound to the exact registration number and the registered promoter entity as filed, and whether any later completion date has since been filed. Where a later date exists, the difference is simple arithmetic between two dated filings — never an estimate, never a verdict. Where none exists, the project sits in the “On original schedule” column, which is most of a healthy corridor.
Our own mandate, Eldeco Echoes of Eden, is listed on the same footing as every other row. A row only appears once both its registered promoter and its filed date can be sourced — so this ledger is deliberately small today and grows as filings are pulled.
Read this before you read a single date
A filed revision to a RERA completion date is a lawful process — an approved extension, a force-majeure re-registration, a sanctioned timeline change. It does not, by itself, indicate fault, and this page never treats it as one. The ledger records dates and their sources; it does not rank projects, assign blame, or describe any promoter’s conduct. If a date has moved, that is a fact you can act on by asking better questions — not a conclusion we’ve drawn for you.
How to read a row, and how to check it yourself
Every row is built from four things you can verify without us: the registration number, the registered promoter exactly as it appears on the filing (not a brand name — the actual legal entity that carries the liability), the RERA-registered completion date, and any later completion date filed since. The difference column is the number of days between the registered date and the date currently on file. When nothing has been re-filed, that difference is zero, and the project sits in “On original schedule.”
The primary source for all of it is the UP-RERA public register. Open the project search at up-rera.in, enter the registration number from the row you care about, and the filing itself will show you the promoter of record and the declared completion date. If a later date has been filed, the record shows that too. This page is a dated, sourced index into that register — it is not a replacement for reading the filing, and it never asks you to take our word over the primary document.
Because a brand and a promoter are not the same thing, the promoter column matters more than it looks. Two projects can share a marketing name and be filed by entirely separate companies with separate track records; this ledger names the entity on the filing so a delivery record attaches to the right company, not to a logo.
Why some corridor projects aren’t on the board yet
The bar for a row is deliberately high, and it keeps the ledger honest even while it’s small. A project appears only when both its registered promoter and its filed completion date can be sourced from the RERA record. That excludes three kinds of project, on purpose:
Reported-but-not-yet-pulled. Where a completion date is currently portal- or developer-stated rather than read from the filing, we either tag it plainly as reported in the row above and invite you to confirm it, or we hold the project back until it’s pulled. Gaur Chrysalis (Phase 1), registration UPRERAPRJ622344/11/2025, is one we’re still sourcing — its exact registered promoter entity and filed completion date haven’t been pulled to our standard yet, so it does not yet carry a row, even though it’s a project on the corridor we know well.
Pre-launch and EOI-only. A project that has not been registered with RERA has no filed completion date to track. Pre-launch and Expression-of-Interest projects therefore cannot appear here at all — there is nothing filed to measure a slippage against. That is a statement about the data, not a comment on any such project.
Regulatory findings that aren’t a date revision. A RERA order about a project is a separate kind of record from a re-filed completion date. This ledger tracks the second, specific thing — two filed completion dates and the days between them — and doesn’t fold in other proceedings, because doing so would turn a clean arithmetic record into an editorialised one.
How each date on the board was sourced
ACE Terra (UPRERAPRJ683816/04/2024) — registered promoter Ajay Realcon India LLP confirmed on up-rera.in (10 Jul 2026), a separate legal entity from ACE Infracity Developers Pvt Ltd, the promoter of the earlier, already-delivered ACE Parkway. The December 2028 completion month is developer- and portal-stated and is tagged reported pending a direct read of the filing.
Eldeco Echoes of Eden (UPRERAPRJ125342/02/2026) — registration and registered promoter Eldeco Sohna Projects Limited confirmed; the January 2031 completion month is read from the RERA filing via our channel record and is tagged reported so you confirm the exact filed date yourself at up-rera.in. Listed here because a tracker that exempted its own mandate would be worthless.
Greenbay The Monarque (UPRERAPRJ710489/10/2025) — declared completion 18 September 2029 confirmed on the project’s own UP-RERA record (11 Jul 2026), a 48-month period from a proposed start of 01 October 2025; registered promoter Green Bay Infrastructure Private Limited. Tagged verified.
Purvanchal Sunbliss (UPRERAPRJ746863/04/2025) — declared completion 29 January 2030 confirmed directly on up-rera.in (11 Jul 2026), registered promoter Purvanchal Projects Private Limited. Tagged verified.
Underlying structured data: corridor.json. UP-RERA does not expose a stable per-project deep link, so each row cites the public project search at up-rera.in plus the exact registration number to enter — the same path we used, reproducible by anyone.
What is a RERA-filed completion date, and can a promoter change it?
It is the completion date a promoter declares to the regulator when a project is registered with UP-RERA. It can be revised, but only through a fresh filing on the RERA record — an approved extension or a force-majeure re-registration, each of which is a lawful process. This ledger records the registered date, and any later filed date, from each project’s own RERA record and cites the registration number so you can pull it yourself.
Does a revised RERA completion date mean a project is in trouble?
No. A filed revision is a lawful step and does not by itself indicate fault. Approved extensions, force-majeure re-registrations and sanctioned timeline changes all happen inside the RERA framework. This page states the dates and their source; it does not assign blame or rate any project. A difference in days is arithmetic between two filed dates, nothing more.
Is Eldeco Echoes of Eden on its original RERA possession date?
Eldeco Echoes of Eden (UPRERAPRJ125342/02/2026, registered promoter Eldeco Sohna Projects Limited) carries a RERA-registered completion date of January 2031. We have found no later RERA-filed revision to that date as of 11 July 2026. Confirm it yourself by entering the registration number at up-rera.in — we include our own project here on the same footing as every other.
How do I check a project's possession date on UP-RERA myself?
Open the project search at up-rera.in and enter the registration number shown in this ledger. The project’s own filing lists the registered promoter and the declared completion date; if a later date has since been filed, the record shows it. That is the primary source — this page is only a dated, sourced index into it, not a substitute for it.
Why isn't every Yamuna Expressway project listed here yet?
A row publishes only when we can source both the exact registered promoter entity and the filed completion date from the RERA record. Projects whose promoter or date we have not yet pulled do not appear, and pre-launch or EOI-only projects have no filed completion date at all, so they cannot appear here. The ledger grows as filings are pulled, never faster than the sources.
Do you include your own projects in this ledger?
Yes. Eldeco Echoes of Eden, the project we represent as an authorised channel partner, is listed on identical footing to every other row — same fields, same source, same self-verify link. A tracker that quietly exempted its own side would not be worth reading, so we do not exempt ours. Run it on us the same way you would run it on anyone else.
