YEIDA Plot Schemes on the UP-RERA Register: 16 Registrations Where the Promoter Is the Authority

Why sixteen Yamuna Expressway registrations name an authority instead of a developer

Almost everything written about the Yamuna Expressway corridor is written about developers. This page is not, and that is the whole point of it.

When a development authority allots residential plots, builds a group-housing block or puts up a shopping complex on its own land, it is the promoter of that project under the Real Estate (Regulation and Development) Act. It registers with UP-RERA like anyone else. The register records this by putting the authority’s own name in the promoter field and setting the applicant type to Competent authority rather than Company. That single field is what separates these sixteen filings from the hundreds of private ones in the same district.

The practical consequence is that a YEIDA plot scheme has a UP-RERA registration number, a registration date, a declared completion date and a document tab, exactly like an apartment project does. Almost nobody reads them, partly because they are genuinely hard to find, for reasons this page spends most of its length on.

One thing to be clear about before the table. We are not YEIDA and we do not act for YEIDA. We hold no scheme brochure, no applicant list, no draw result and no allotment letter, and we will not pretend otherwise; those live with the authority and are published on its own site. What we hold is a mirror of the UP-RERA register, and what this page publishes is what that mirror says about these sixteen filings.

The sixteen registrations, as the register holds them

Five fields per row, all of them copied rather than derived, in registration-date order. Each name links to that filing’s record page on our register tracker, which carries the fuller set of fields we hold for it.

The scheme name on the register is not the scheme name in the brochure

Here is the finding that makes this page worth bookmarking. Ten of these sixteen rows carry an RPS or RRPS scheme code in the registered name, and the register writes that code four different ways.

• Hyphen. RPS-04/2021, RPS-06/2022, and RPS-02, SEC-22D.
• A space. RPS 05/2021.
• Nothing at all. RPS07/2023, RPS08/2024, RPS09/2025, RPS10/2025, and RPS01 inside row 8.
• A space and then a hyphen. RRPS -04/2020, where the space sits between the prefix and the hyphen rather than after it.

Row 8 is its own category. Its registered name is RPS01,RRPS01 AND RRPS02 (SECTOR 18 AND 20) ,YEIDA: three scheme codes joined by commas and the word AND, with a stray space before the final comma, all inside a single registration. If you are looking for RRPS02 as a standalone filing in this set, you will not find it as its own row, because on the register it lives inside that one.

And row 5, INDIVIDUAL RESIDENTIAL PLOTS, SEC-17,YEIDA, is a residential-plot filing that carries no scheme code whatsoever. A search built around the letters RPS misses it completely. That is the eleventh plot-named row, and it is the clearest illustration of why a code-based search is the wrong tool here.

One more string worth knowing, because it will cost you a search otherwise. The promoter cell on all sixteen rows holds a single identical string, and it reads YAMUNA EXPRESSWAY INDUSTRIAL DEVLOPMENT AUTHORITY - with DEVLOPMENT spelled that way in the field we hold, copied from the register as read on 29 July 2026. We print it verbatim rather than tidying it, because a promoter-name search that uses the correctly spelled word may not match these rows. This is a note about a text field and nothing else.

What the register calls RPS-10, and why the year in a scheme label is not the year it registered

The scheme that drew the largest public interest on this corridor in 2026 is registered under the name RPS10/2025, on registration number UPRERAPRJ307764/03/2026, registered 14 March 2026. Coverage of that scheme, ours included, calls it RPS-10/2026. Both are correct about different things, and the difference is worth understanding rather than smoothing over.

A scheme label is the authority’s own naming of its scheme. A registration date is when UP-RERA registered the filing. On seven of the eight RPS and RRPS filings on this page that carry a year in the name, the label year and the registration year agree: RRPS -04/2020 registered in 2020, RPS-04/2021 and RPS 05/2021 in 2021, RPS-06/2022 in 2022, RPS07/2023 in 2023, RPS08/2024 in 2024, RPS09/2025 in 2025. RPS10/2025 is the row where they part company, registering in March 2026 under a 2025 label.

The registration number itself settles the argument. The suffix /03/2026 encodes March 2026, which matches the registration date exactly, and that suffix convention is the one our decoder page found holding across every slashed number in the mirror. So when a listing, a forum post or an assistant tells you the RPS-10 registration is a 2025 filing, the number on the filing says otherwise.

There is a second reason to keep this row in view. Its register address field, one of only three populated across these sixteen, reads POCKET- 9A, SECTOR-18, BLOCK A & B, SECTOR-15C, SECTOR-24A-YEIDA, GAUTAM BUDH NAGAR. That is the authority’s own filing naming Sectors 18, 15C and 24A - the same three sectors the scheme coverage reports. Two independent record types agreeing is worth more than either alone, and it is the kind of cross-check we would rather publish than a confident sentence. The other two populated address cells are PLOT-1B on RPS08/2024 and POCKET-9B on RPS09/2025. The remaining thirteen are empty, which is why this page carries no sector column: inventing one would be a guess.

Which of the sixteen are plot schemes, and which are something else

The register carries no scheme-type field. There is no cell that says “residential plot scheme” or “group housing”, so any grouping here is a reading of the registered name string, not a register fact, and we are labelling it as ours. The test is mechanical: does the registered name contain an RPS or RRPS code, or the word PLOTS? Eleven rows do. Five do not.

A caution on scheme numbers, because absence is easy to over-read. Among these sixteen rows the RPS and RRPS codes that appear are 01, 02, 04, 05, 06, 07, 08, 09 and 10, with 04 appearing under both prefixes as two separate filings: RRPS -04/2020 and RPS-04/2021 carry separate registration numbers. Codes 01 and 02 also appear under both prefixes, but with the RRPS forms sitting inside row 8 rather than on rows of their own. No row in this set carries an RPS-03 code. That is a statement about these sixteen rows on 29 July 2026 and nothing more; it is not a claim that no such scheme exists, and you should not treat it as one.

What the document count on each filing does and does not tell you

The last column of the main table is the number of rows listed on that filing’s document tab in our mirror. It is a count of listed rows. We did not download the files, we did not open them, and we are not in a position to tell you what any of them contain.

Each of those rows carries a status label set by the portal itself. Our mirror holds three such labels across this set: New, Old and NA. We print the split below because a bare total hides it, and because a reader who wants to interrogate this data deserves to see the shape of it rather than a single number.

What a document tab is useful for is the thing a count can never do for you: opening it. The entries worth your own eyes are the proforma of the allotment letter, the proforma of the agreement for sale, the development work plan and the encumbrance details, because those are the papers whose wording governs what you sign. A number in a column here is a pointer to them, not a substitute.

Five things to read on an authority filing before you apply

This is the decision framework, and every step in it is grounded in a field that appears on this page.

1. Match by number, never by name. Take the registration number for the scheme you are being shown from the table above and confirm it against the document you were handed. If it is not in this table, that is not a problem with the document; it may be a filing outside our scope, and the register itself is the place to settle it.
2. Confirm the promoter really is the authority. On the live filing, check that the promoter field holds the authority’s string and that the applicant type reads Competent authority. A scheme run by the authority and a private project standing on YEIDA land are different transactions with different counterparties, and the applicant-type field is the fastest way to tell them apart.
3. Read the declared completion date for what it is. It is the date the promoter declared at filing. It is not a handover guarantee, it is not a promise made to you, and it is not something to subtract today’s date from. The date that binds anyone is the one written into your own allotment letter or agreement for sale. Read that document, and read it before you pay.
4. Open the document tab rather than counting it. Go to the proforma of the allotment letter and the proforma of the agreement for sale first. Those two tell you what you are actually agreeing to, in the authority’s own drafting, before any brochure gets a say.
5. Take every rupee figure from the authority, not from a register row and not from us. Rate, module size, deposit percentage, application fee, refund window and draw mechanics are scheme-brochure facts published by YEIDA. Our sourced reading of the RPS-10 figures is at RPS-10 by the numbers, with a confidence tag on every one, and even that page tells you to confirm against the brochure.

How to verify every row on this page yourself

1. Open up-rera.in. Use the site root; deep links into the portal’s project paths do not reliably resolve, so a bookmarked inner URL is more likely to fail than to help.
2. Go to the registered-projects search and search by registration number, pasting it exactly as printed in the table, slashes included. For pre-2024 filings there is no slashed suffix, so UPRERAPRJ8756 is the whole number.
3. If you would rather search by promoter, paste the promoter string verbatim from the section above, including its spelling. Searching the district of Gautam Buddha Nagar and reading down the promoter column also works, and is slower but harder to get wrong.
4. On the filing that opens, read the promoter name, the applicant type, the registration date, the declared completion date and the document tab, and compare them against the row here.
5. If a cell on this page disagrees with the live filing, the live filing is right and we are out of date. Tell us and we will correct the page and say that we did.

What this page counts, what it leaves out, and the date the register was read

The filter, stated so you can rerun it. Two conditions, both exact-match on register fields: promoter name equals the register’s own string for the authority, and applicant type equals Competent authority. No date window, no address test, no keyword search on the name. Our mirror holds 966 registrations for Gautam Buddha Nagar spanning registration years 2017 to 2026; those two conditions return 16 of them.

What was excluded, and why. Three exclusions, each deliberate. First, the mirror holds 27 registrations of applicant type Competent authority in total, of which 16 are YEIDA’s; the other 11 were filed by the Greater Noida Industrial Development Authority and the New Okhla Industrial Development Authority. They are excluded because they are other authorities’ filings in other jurisdictions, not because of anything about them. Second, a promoter-name search on the word Yamuna also returns a registration whose promoter is YAMUNA BUILTECH PRIVATE LIMITED, a company. It is excluded because its applicant type is Company, not Competent authority: a similar name is not the same counterparty, and this is exactly the trap the applicant-type field exists to catch. Third, every project registered by a private developer on YEIDA land is excluded, because on those filings the promoter is that company and the counterparty in your transaction is that company. Our register work on the named private projects along this corridor is a separate page, Yamuna Expressway RERA numbers.

The fields this page publishes, and the ones it does not. Five fields per row and no others. We publish no promoter phone number or email address. We publish no revised completion date, no extension record and no complaint count for any row, and we run no arithmetic between two register fields, because the moment a page does that it is publishing its own opinion dressed as a register fact. We publish no sector column, because the register’s address field is empty on 13 of these 16 rows and a parsed sector would be a guess on most of them. We publish no rate, plot count, module size, deposit or application figure, because none of those are register data and because our figure work already lives on its own page, which we would rather you cite than a weaker restatement here.

What a declared completion date is, once more, because it matters. It is the completion date the promoter itself declared when it filed. It records what was declared, on the day it was declared. It is not a guaranteed handover date and not a commitment made to you. The binding date is the one in your own agreement for sale or allotment letter, and the only place to read that is the document itself.

What we sell, stated plainly. Vidastu Advisory is a UP-RERA-registered agent, not a developer and not an authority. We hold no agency, appointment or arrangement of any kind with YEIDA, and we represent none of the 16 registrations on this page, because on every one of them the promoter is a government body. What we sell on this corridor is advisory and construction, and if you have read this page and want a second pair of eyes on a filing, the desk is below. Nothing here is an offer, an invitation to apply, a solicitation, investment advice, or tax or legal advice, and no return, appreciation, rental yield or tax outcome is stated or implied.

For neighbouring register work, our corridor pages are the corridor live index, the YEIDA sector guide for 22D, 22A, 18 and 20, and the corridor price history.

Frequently asked questions

Vidit Kaushik

Civil Engineering, BITS Pilani · UP-RERA Agent UPRERAAGT000309/01/2026 · Founder, Vidastu Developers Pvt. Ltd.