ReraGenieLog inGet a buyer report

Home / Developers / YASH DEVELOPERS UNIT OF VIKRANT V RAIKAR HUF

YASH DEVELOPERS UNIT OF VIKRANT V RAIKAR HUF: RERA track record

Others ยท attribution by exact filing name, entity resolution in progress

YASH DEVELOPERS UNIT OF VIKRANT V RAIKAR HUF has 1 registration on MahaRERA, including Bhiva Tower. Its filings disclose 1 earlier MahaRERA project: declares 1 of 1 past projects completed on time. Litigation is declared on 1 of its registrations.

1RERA registrations
1Past projects disclosed
on timeMedian delivery slip
1Registrations with litigation
Follow this developer. An email when YASH DEVELOPERS UNIT OF VIKRANT V RAIKAR HUF registers a new project on MahaRERA, and when the filings of their existing projects change: new sales, moved possession dates, extensions, complaints. Runs 12 months, no auto-renew. Follow · Rs 999 / 12 months

Projects by this developer

Showing the one project.

Largest first, by the unit count in the filing.

ProjectLocationUnitsBookedRegisteredStatus
Bhiva TowerP52000045952Navi Mumbai, Raigarh, 410218--15 Jun 2022Registered

What this promoter declares as its own experience

YASH DEVELOPERS UNIT OF VIKRANT V RAIKAR HUF declares experience on 1 earlier project. It carries no registration number we could match on MahaRERA, which is usual for work done before the register existed.

From the promoter experience table each promoter files with MahaRERA, matched to the register by registration number. A declaration naming another promoter's project is a claim of involvement, and involvement takes several shapes: a parent and its project company, one firm re-registering under a second name, or a joint venture between two separate developers. We publish the claim as filed and do not treat it as proof that the entities are one builder.

Past projects, as disclosed in RERA filings

ProjectPromised completionActual completionDelivery
Shruti Apartment
31 May 202321 Apr 2022On time

Frequently asked questions

How do I verify YASH DEVELOPERS UNIT OF VIKRANT V RAIKAR HUF as a legal entity before signing?

Your agreement for sale must name the exact entity registered for the project, not a group brand. The registration certificate on each project's MahaRERA page names the exact legal entity; ask for it if the sales office only uses a brand name. Large builders commonly register one company or LLP per project, which is normal; the entity on the registration certificate is the one legally accountable to you.

How should I use this delivery record when booking with YASH DEVELOPERS UNIT OF VIKRANT V RAIKAR HUF?

Their completed projects have landed on time so far, but apply the same test to the specific project: promised date, current progress, and sales pace. If possession then slips past your agreement date, section 18 entitles you to interest at SBI's highest MCLR plus 2 percent (currently 10.90% per annum) for every month of delay, or an exit with a full refund with interest.

Does the declared litigation make YASH DEVELOPERS UNIT OF VIKRANT V RAIKAR HUF unsafe to buy from?

Not by itself. Litigation on a registration ranges from a boundary dispute to an allottee case about delay; what matters is the case type, which court or forum, and whether it touches the land title of the project you are buying. The case list is in each project's filed documents. Treat litigation as a question to resolve in writing before booking, not as a verdict either way.

Spotted a project attributed to the wrong developer, or something else wrong on this page? Projects are grouped by the promoter name as filed, so a firm that registers under two spellings can split across two pages. Tell us and we will check it against the filings.

Report an errorShare feedback

Data from official MahaRERA filings. How we handle corrections is on the about page.

Report an error or share feedback

About the YASH DEVELOPERS UNIT OF VIKRANT V RAIKAR HUF developer page. Projects are grouped by the promoter name as filed, so a wrongly attributed project is the most useful thing to report.

We read every report. We cannot promise a reply to each one.