SNN Sarjapur Road Project Details: Apartments, Status and Approvals

The developer is SNN Raj Corp, operating here through SNN Properties LLP (LLPIN AAA-8330, incorporated 2012), registered at Elephant Rock Road, Jayanagar 3rd Block, Bengaluru 560011. The group traces its brand heritage to 1994 and states 40 completed projects delivered by a 300-strong team. Its own published built-up figures vary between documents — the about-us page and the homepage counter do not agree — so the project count of 40 is the stable number to work from rather than any square-footage claim.

Leadership is Shah Sanjay (Founder and Managing Director) and Shivashankar Bhat (Founder and Director), with Neelu Jain heading sales and marketing, alongside directors Ashish Bhandari, Anuj Sanjay Jain and Shah Akshat. The completed portfolio includes SNN Raj Etternia, SNN Clermont, SNN Raj Grandeur, SNN Raj Greenbay, SNN Raj Spiritua, SNN Raj Serenity, SNN Raj Neeladri and SNN Raj Lakeview; ongoing work includes Raj Bay Vista, Raj Viviente and Raj High Gardens.

One clarification is load-bearing for anyone running due diligence: SNN Raj Corp registers each project under a separate LLP or SPV — SNN Properties LLP holds Etternia and High Gardens, SNN Homes LLP holds Greenbay, SNN Abode LLP holds Viviente, SNN Arjun Builders LLP holds Bay Vista. This is ordinary practice and ring-fences each project's liabilities, but it means the promoter entity on one RERA certificate does not carry the portfolio of another. Establish which vehicle holds this project before you commit. The developer's SNN Electronic City project sits on the other side of the Yellow Line corridor and is a useful reference point for how SNN Raj Corp builds at scale.

Two land extents are on record and they do not reconcile:

• 30.66 acres — the project information sheet.
• 11.6321 hectares = 28.74 acres — the Common Application Form.

The most likely explanation is the standard gross-versus-declared gap: the information sheet reports the gross parcel as acquired, while the CAF declares the net extent after statutory deductions such as road widening set-backs, buffer surrenders and any portion excluded from the application boundary. Support for that reading sits inside the filing itself — the Revised ToR states a development area of 1,21,758.77 sq m, which works out to 30.09 acres, a figure between the two. Both numbers are published here because neither has been formally reconciled, and the difference of roughly 1.9 acres is material enough that it should be confirmed against the sanctioned plan before purchase.

The layout is seven towers, lettered A through G, subdivided into 15 wings, plus a freestanding amenity block. Every residential tower is 2 Basement + Ground + 24 upper floors to a height of 79.95 m — just under the 80 m threshold that triggers the heaviest high-rise compliance regime. The amenity block is Basement + Ground + 3 floors at 21 m, which is a genuinely large clubhouse envelope rather than a podium level carved out of a tower.

The scale arithmetic is instructive. Total built-up area is 5,52,042.27 sq m — about 5.94 million sq ft. Against the development area of 1,21,758.77 sq m, an FAR of 3.26 accounts for roughly 3,96,900 sq m of that, leaving approximately 1,55,100 sq m in non-FAR area, which is what two full basement levels of parking and services across a footprint this size would be expected to occupy. Ground coverage of 13.19% puts the total building footprint at 16,056.44 sq m across eight structures — an average of about 2,000 sq m per building, consistent with slim, wing-based tower plates rather than bulky slabs.

Parking is 4,900 car bays. Against the higher of the two unit counts that gives just over two bays per home; against the lower, closer to 2.4. Either way this is a two-car provision, which points to a mix weighted toward 3 and 4 BHK rather than compact stock.

The unit count is the single least settled number in the file. Two figures appear — 2,075+ and 2,359 — and the source document itself records the current count as Not Available. The utilities sizing offers a useful cross-check: fresh water demand of 1,156 KLD at the standard 135 litres per capita per day implies a design population of roughly 8,500 residents, and solid-waste generation of 5,276 kg/day at 0.62 kg per person points to the same figure. At a typical 3.6 occupants per home that is consistent with the higher, 2,359-unit reading. This is an inference from the engineering, not a confirmation — but it suggests the infrastructure has been sized against the larger number.

The environmental undertakings in the filing are specific enough to be checked later, which is the only kind worth publishing.

Water is designed as a closed loop wherever possible. Against 1,566 KLD of wastewater, the STP train delivers 1,620 KLD of installed capacity and 1,488 KLD of treated output — more than enough to cover the entire 585 KLD flushing demand and the full landscape irrigation load, with the surplus routed to horticulture and common-area use. Forty-one rainwater recharge pits handle groundwater replenishment across the parcel.

Planting is quantified. 2,300 trees across twelve species are committed — Kadamba, Neem, Gulmohur, Jacaranda, Champa, Nagalinga Pushpa, Bilvapatre, Bael, Devil's Tree, Asoka, Arjun and Jamun. Across 49,829 sq m of landscape that is roughly one tree per 22 sq m, and the species list is native and mixed rather than the single-species avenue planting that reads well on a plan and fails in year three.

Solid waste is segregated at source, with the 5,276 kg/day load split into 2,110 kg organic and 3,166 kg inorganic streams — the organic fraction sized for on-site composting. Solar generation is proposed but not yet quantified in the filing, and diesel backup is provisioned at 5,000 KVA against a 9,170 kW sanctioned load, about 44% of the connected demand.

The low ground coverage figure of 13.19% is the number that ties this together. Building on an eighth of the site and landscaping 40.9% of it is what makes the tree count, the recharge area and the open horizon along the southern lake edge physically possible at the same time.

Four things on this page are not settled, and a buyer should treat them as inputs to a question rather than as facts:

1. Unit count. 2,075+ or 2,359, with the source document recording the current count as Not Available. The utilities sizing leans toward the higher figure.
2. Unit sizes and configuration mix. One source runs a size ladder from 1 BHK to 5 BHK across eight tiers; an earlier unit mix shows no 1 BHK at all. The 2, 3 and 4 BHK core is where both sources overlap and is the only part that should be planned around.
3. Launch and possession dates. Q1 2027 and Q1 2032, both explicitly tentative, neither RERA-committed.
4. Land extent and buffers. 30.66 versus 28.74 acres, and lake/nala buffers of 24/10 m in the ToR narrative against 30/15 m on the site-plan drawing.

Every one of these resolves at RERA registration, which is when the sanctioned plan, the unit inventory, the carpet-area schedule and a legally enforceable completion date all enter the public record at once. Until then, what this project offers is an unusually well-documented statutory position on a ~30-acre lake-edge parcel inside the metro catchment — and a set of numbers that will be worth re-reading against the registration certificate the day it is issued.