Diversity grouped from RERA project_type. Sell-through, completion %, delays and upcoming handovers
derived from total_units, units_sold, completion_percent,
proposed_completion & actual_completion across all merged promoter entities.
| Project | RERA Reg | Status | District | Area | Map | Website |
|---|---|---|---|---|---|---|
| vasu appartments | PCGRERA280618000384 |
Ongoing | Bilaspur | - | Map | - |
| # | Complaint No. | Applicant | Section | Date | |
|---|---|---|---|---|---|
| 1 | M-EXE-2020-00975 | SMT. KIRAN BHAJAGAWALI, W/O SHRI RAJESH BHAJAGAWALI | Section 40,Section 36, Section 37 | 27 Feb 2021 | |
| 2 | M-EXE-2020-00977 | SHRI AJAY KUMAR PANDEY, S/O SHRI MUKHDEV PANDEY | Section 40 | 11 Jan 2021 | |
| 3 | M-EXE-2020-00976 | SMT. SARITA SINGH, W/O SHRI V. R. SINGH, | Section 40 | 11 Jan 2021 | |
| 4 | M-EXE-2020-00974 | SMT SHOBHNA SINHA, W/O SHRI PRAKASH KUMAR SINHA | Section 40 | 11 Jan 2021 | |
| 5 | M-PRO-2019-00547 | SHRI AJAY KUMAR PANDEY, S/O SHRI MUKHDEV PANDEY | Section 18 | 28 Sep 2019 | |
| 6 | M-PRO-2019-00546 | SMT. SARITA SINGH, W/O SHRI V. R. SINGH, | Section 18 | 28 Sep 2019 | |
| 7 | M-PRO-2019-00545 | SMT. KIRAN BHAJAGAWALI, W/O SHRI RAJESH BHAJAGAWALI | Section 18 | 28 Sep 2019 | |
| 8 | M-PRO-2019-00544 | SMT SHOBHNA SINHA, W/O SHRI PRAKASH KUMAR SINHA | Section 18 | 28 Sep 2019 |
| Factor | How it's calculated | Raw Value | Score (0-100) | Weight | Weighted |
|---|---|---|---|---|---|
| Builder-Level RERA Compliance Score | 1 project(s): 1 Partial(50) | 50/100 |
50
|
60% | 30.0 |
| Orders & Violations | 8 order(s) under 3 distinct RERA section(s). Score = max(0, 100 - 3 x 4) = 88 | 3 section(s) |
88
|
40% | 35.2 |
| Complaints Filed | 8 complaint(s) total. Only complaints with actual orders affect the score (via "Orders & Violations" factor above). | 8 | Info only — not scored | ||
| Buyer Rating | Average buyer review rating across all projects by this builder. | No reviews | Info only — not scored | ||
| Order Details | |||||
| Weighted Sum / Total Weight | 100% | 65.2 | |||
| Final Normalized Score | 65/100 | ||||
Avg. Completion % = SUM(effective_completion) / COUNT(projects with completion_percent NOT NULL)
completion_percent = 100
while their registration_status is still Ongoing / New and no
actual_completion date is filed. Per RERA, a project is only formally complete when
status = Completed OR actual_completion is set. So we cap such projects at
99% for averaging. Capped rows below are marked
CAPPED.
seemankan1.projects.completion_percent · Excludes projects with NULL completion.
| Project | RERA | Status | Reported | Effective % |
|---|---|---|---|---|
| vasu appartments | PCGRERA280618000384 |
Ongoing | 100% | CAPPED 99% |
| SUM ÷ COUNT | 99 ÷ 1 = 99% | |||
proposed_completion < today (25 Apr 2026)registration_status ≠ Completed AND actual_completion is NULL/emptycompletion_percent is intentionally not used here because RERA developers
self-report 100% even while the project is still Ongoing. Only the formal status / actual completion
date proves the project is closed.
| Project | RERA | Status | Proposed Completion | Completion % | Days Overdue |
|---|---|---|---|---|---|
| vasu appartments | PCGRERA280618000384 |
Ongoing | 05 May 2019 | 100% | 2,547 d |