Kada Agrahara, Sompura Gate or Sarjapura? One Project, Three Filings

One SUYUG community on the Sarjapura stretch of the corridor is filed by listing portals under three different locality names: Sarjapura, Sompura Gate and Kada Agrahara. Its registration certificate names one village and one hobli. Nobody has corrected the portals, and nobody will.

This happens constantly and it is worth understanding as a mechanism rather than as an accusation, because the fix is the same either way: use the document, not the dropdown.

Three locality labels, one project, no correction anywhere

The three labels are not equally wrong. Sarjapura is a revenue village and also the hobli name. Sompura Gate is a junction on that stretch. Kada Agrahara is a separate locality in the same taluk. A reader looking at three tabs sees three addresses and reasonably concludes there are three projects, or that somebody is being evasive. Neither is true. What they are seeing is three data-entry decisions.

Why aggregator locality fields drift

A listing's locality is a category, chosen from a dropdown the portal maintains, by a person whose objective is that the listing surfaces for searches buyers actually run. That is a reasonable objective and it produces predictable drift:

• Search volume pulls the label. A better-known nearby name attracts more traffic than the correct but obscure one, so listings migrate toward it.
• The dropdown may not contain the right answer. If the portal's locality list has no entry for the actual village, the nearest available option is picked.
• Multiple parties create listings. A developer, several channel partners and the portal's own content team can each file the same project, each choosing differently.
• Nothing reconciles them. No portal cross-checks its locality field against a registration certificate, because it has no access to one and no obligation to look.

The result is metadata that describes the marketplace's taxonomy, not the land.

The tiebreak: what the certificate records

A registration certificate does not carry a locality. It carries survey numbers inside a named revenue village, inside a hobli, inside a taluk. For the community in question the line reads: Sy. No. 516, Sarjapura Village, Sarjapura Hobli, Anekal Taluk, under registration number PRM/KA/RERA/1251/308/PR/140825/008000.

That single line settles all three portal labels at once. It is not a locality, so it does not compete with them; it is the address the state recognises, and the locality labels are commentary on it.

Why this is not pedantry

A wrong locality label is harmless right up to the moment you try to do something with it. Then it breaks four things in sequence:

Kada Agrahara as a place: what is verifiable

Since the name is in the title of this piece, here is what can be stated about it and what cannot.

• Verifiable: it is a name in use on this corridor and falls in Anekal taluk, Bengaluru Urban district, Karnataka. Anekal is one of the district's five taluks. Any real-estate project on land in this district is registered with the Karnataka authority, and a deed there is registered through the Karnataka Department of Stamps and Registration.
• Not stated here: the hobli. The district administration's own table gives Anekal taluk four hoblis and names none of them, and we found no government page naming the hobli for this locality. A blank you can see is more useful than a value you cannot check.
• Not stated here: the gram panchayat or urban local body, and the sub-registrar's office for any particular parcel. Both are parcel-level answers, and sending a reader to the wrong counter is the error on a page like this that cannot be walked back.
• Our interest, declared: SUYUG builds nothing at Kada Agrahara — nothing ongoing, nothing announced. There is no version of this article that sells you anything, which is why it can be written plainly.

The five-minute check that settles a locality dispute

1. Ask the developer for the registration certificate as a file, and read the land description off it.
2. Search the registration number on the authority's public register and confirm the two match.
3. Write down the survey number, village, hobli and taluk exactly as printed. That is now your address for every records step.
4. Ignore every locality label from that point on, including the one the developer's own marketing uses.
5. If no certificate exists because the project is not registered, you have learnt something more important than the locality.

Step five is not a rhetorical flourish. Section 3(1) of the Real Estate (Regulation and Development) Act, 2016 prohibits advertising, marketing, booking or selling an unregistered project, so an advertised project with no registration to show is the finding, not a gap in your research.

Our registrations, with the land as printed on each certificate, are on the registrations page; the community whose certificate is quoted above has its own page at Saffron. To work a corridor name down to district, taluk, hobli and regulator yourself, use the jurisdiction finder, which shows its sources and marks the rows it cannot verify.