TL;DR
- ULPIN (also branded Bhu-Aadhaar) is a 14-digit, geo-referenced unique ID generated from a land parcel's latitude/longitude under the central DILRMP programme — it links a single parcel's ownership record, mapped boundary and land type into one reference, and matching a plot's ULPIN and its Bhu-Naksha boundary to the deed is one of the cleanest ways to catch survey-number fraud.
- It is not a title guarantee, an ownership certificate, or proof the seller owns the land. It is an identifier for the parcel, like a permanent address — what attaches to it (RTC, mutations, encumbrances) is what you actually diligence.
- One survey/hissa equals one ULPIN. If a seller's deed, RTC and the on-ground GPS pin do not all resolve to the same ULPIN, you may be looking at a different parcel than the one being sold.
- Coverage is real but uneven: many states (including Karnataka) have assigned ULPINs to a large share of parcels, but un-surveyed, sub-divided, or disputed land may have no ULPIN or a stale boundary yet.
- For lenders and investors, ULPIN is a forward-looking way to pin collateral to a fixed map object across re-numbering and sub-division — but in 2026 it supplements, it does not replace, a lawyer-reviewed title search.
What is ULPIN / Bhu-Aadhaar, in one sentence?
ULPIN (Unique Land Parcel Identification Number), marketed as Bhu-Aadhaar, is a 14-digit geo-referenced identifier assigned to a single land parcel under the central government's Digital India Land Records Modernization Programme (DILRMP), derived from the parcel's surveyed latitude and longitude.
Think of it as a permanent "PIN code for a plot." Just as Aadhaar gives a person one number that follows them across documents, ULPIN gives a parcel one number that should stay constant even as survey numbers get re-drawn, hissas get split, or records get digitised. Because it is generated from the geo-referenced cadastral map and the parcel's coordinates, the ID is anchored to a location on a map, not to a piece of paper that can be re-typed or duplicated.
What ULPIN is NOT (the myth-buster)
This is the part that trips people up, so be precise:
- ULPIN is not a title. It does not tell you who owns the land or whether the title is clean. It identifies the parcel; ownership lives in the RTC/record-of-rights and the registered deeds.
- ULPIN is not a "land Aadhaar" you apply for. The "Bhu-Aadhaar" branding invites that confusion. It is generated by the revenue/survey department from official survey data — an owner does not create it.
- ULPIN is not proof the boundaries are correct on the ground. It reflects the cadastral map's geometry, which can be outdated or imprecise, especially for old or sub-divided parcels.
- ULPIN is not yet universal. A parcel without a ULPIN is not suspicious by itself; large tranches of land are still being surveyed and assigned.
For the bigger picture of how an identifier fits into actual title work, see what a Title Search Report covers.

How do I find a parcel's ULPIN?
You read it off official land records, not off the deed. The same parcel's ULPIN should appear consistently across the record-of-rights and the cadastral/GIS map. The exact label and portal vary by state, but the logic is identical pan-India.
| State | Where ULPIN typically appears | Equivalent record to cross-check |
|---|---|---|
| Karnataka | RTC (Bhoomi Pahani) header; K-GIS / Dishaank parcel attributes; e-swathu / property records | Bhoomi RTC + Bhu-Naksha / K-GIS boundary |
| Maharashtra | Increasingly on the 7/12 extract and property card | 7/12 (Satbara) extract |
| Telangana | Record-of-rights / Dharani parcel data | Dharani / Bhu Bharathi record |
| Tamil Nadu | Patta / parcel data as ULPIN rollout proceeds | Patta and Chitta |
In Karnataka specifically, the cleanest source is the geo-referenced parcel layer behind K-GIS / Dishaank. That layer carries the ULPIN as an attribute on the hissa-level parcel, alongside the hissa number, surnoc and the national LGD village code — which is exactly how an automated diligence pipeline resolves a survey number plus hissa to a single map object and reads its ULPIN. (This is the same parcel-as-anchor logic Deedwise uses internally: every record gets tied back to one geo-referenced parcel.)
Reading the structure (without over-reading it)
The 14 digits are not random — they are derived from the parcel's geo-referenced coordinates and its place in the official survey records. You do not need to decode the digits yourself, and you should not try to infer ownership or area from them. Treat ULPIN as an opaque key for matching, and let the attached records tell you the substance.
How do I use ULPIN in due diligence?
Use it as the join key that forces every document, map and field visit to refer to the same physical parcel. The single highest-value move is a three-way match.
The three-way ULPIN match
- Deed-to-record: Take the survey/hissa described in the sale deed and the seller's RTC/record-of-rights, and confirm both resolve to the same ULPIN.
- Record-to-map: Pull the parcel's Bhu-Naksha / cadastral boundary for that ULPIN and confirm the shape, neighbours and approximate area are consistent with the RTC area and the deed schedule.
- Map-to-ground: Drop a GPS pin at the actual plot and confirm its coordinates fall inside the ULPIN's mapped boundary.
If all three line up, you have strong evidence that the parcel being sold is the parcel on paper. If they diverge, you have caught a classic survey-number / boundary mismatch before money moves — one of the most common and expensive defects in Indian land deals.
This matters most for transactions where the schedule of property is vague or hand-drawn, where a large survey number was sub-divided into many hissas, or where the same survey number appears in adjoining villages. ULPIN cuts through that ambiguity because two different parcels cannot share one ULPIN.
Where ULPIN fits in the 4-pillar workflow
| Pillar | What ULPIN helps with | What still needs the actual record |
|---|---|---|
| Ownership | Confirms which parcel the 30-year chain refers to | The chain of title, mutations, succession |
| Land | Anchors the boundary, area and land type to one map object | Patta type, conversion status, Column 11 RTC entries, zoning |
| Encumbrance | Ensures the EC/mortgage search is run against the right parcel | The actual EC, CERSAI and bank charges |
| Litigation | Ties any case to a verifiable parcel ID | Court records by party and property |
A fuller, scannable version of this lives in the developer's due diligence checklist.
What can ULPIN NOT tell you? (the honest limits)
ULPIN is a powerful anchor, but it is silent on almost everything a buyer actually worries about. Knowing these limits is what separates real diligence from a false sense of safety.
- It says nothing about title. A perfectly valid ULPIN can sit on a parcel with a forged chain of title, an unreleased mortgage, or a live partition suit. ULPIN identifies; it does not certify.
- The boundary can be wrong or stale. Geo-referenced cadastral maps inherit decades of survey error. A ULPIN boundary that overlaps a road, a tank, or a neighbour's wall on the ground is a flag to investigate, not a fact to trust blindly.
- Sub-division lag. When a parent survey number is split, child ULPINs and updated boundaries can lag the revenue records — so the "current" ULPIN map may not match the latest hissa reality.
- No ULPIN is not proof of a problem. Un-surveyed, forest, government, or newly converted land may simply not have a ULPIN assigned yet.
- Branding confusion is exploited by fraudsters. Because "Bhu-Aadhaar" sounds like an ownership document, a seller may flash a ULPIN as if it proves ownership. It does not. Always pull the underlying RTC, encumbrance certificate and registered deeds — see how to verify property title end-to-end.
In short, ULPIN tells you which parcel with high confidence. It tells you nothing reliable about who owns it, what it can be used for, or what is charged against it — and several of the most common title defects in Indian real estate hide precisely in that gap.
How does ULPIN relate to other land records and to encumbrances?
ULPIN is the spine that the other records hang off, not a substitute for any of them. The record-of-rights (RTC / 7-12 / patta) tells you ownership and cultivation; the cadastral map (Bhu-Naksha) tells you geometry; the encumbrance certificate and registered deeds (in Karnataka via Kaveri Online 2.0) tell you what is registered against the parcel. ULPIN's job is to guarantee all of them are talking about the same piece of land.
The practical payoff for lenders and investors: when collateral is pinned to a ULPIN rather than a survey number that can be re-numbered after sub-division, you can track that exact parcel across time and across record systems. That is the long-term promise of DILRMP — one parcel ID feeding ownership, boundary and land-type into a single source of truth. As of 2026, that promise is partly delivered and unevenly so, which is why the working rule remains: AI and portals gather and match the data; a qualified lawyer reviews the chain and signs off on the title.
Frequently asked questions
Is ULPIN the same as Bhu-Aadhaar? Yes. Bhu-Aadhaar is the consumer-facing brand name for the Unique Land Parcel Identification Number (ULPIN). Both refer to the same 14-digit, geo-referenced parcel ID assigned under the central DILRMP programme. "Bhu-Aadhaar" is marketing; "ULPIN" is the technical term you will see in records and documentation.
Does a ULPIN prove who owns the land? No. ULPIN identifies the parcel, not the owner. Ownership lives in the record-of-rights (RTC in Karnataka, 7/12 in Maharashtra, patta in Tamil Nadu, etc.) and in the registered deeds. Treat a ULPIN as a permanent address for the plot, then verify ownership, encumbrances and the chain of title separately — ideally with a lawyer-reviewed title search.
How is a ULPIN generated and is it really unique? It is generated by the state survey/revenue department from the geo-referenced cadastral map using the parcel's latitude and longitude, so each surveyed parcel gets one and only one ULPIN. Because it is tied to a location on the map, two different parcels cannot share the same number, which is what makes it useful for catching survey-number mismatches.
Where do I find the ULPIN for a plot in Karnataka? It typically appears on the RTC (Bhoomi Pahani) and as an attribute on the geo-referenced parcel in K-GIS / Dishaank, alongside the hissa number and LGD village code. The reliable check is to confirm the same ULPIN shows up on the RTC, on the Bhu-Naksha boundary, and that a GPS pin at the actual plot falls inside that boundary.
What if the parcel has no ULPIN? A missing ULPIN is not automatically a red flag — large amounts of land are still being surveyed and assigned numbers, and un-surveyed, forest or government land may not have one. It does mean you cannot rely on the ULPIN three-way match, so lean harder on the RTC/record-of-rights, the cadastral map, the encumbrance certificate and a physical boundary verification.
Can I rely on ULPIN instead of a full title search? No. ULPIN confirms which parcel you are dealing with, but says nothing about clean title, unreleased mortgages, pending litigation, or land-use restrictions. It is a strong anchor for diligence, not a replacement for it — the data still needs a lawyer to review the chain of title and sign off.
Continue reading

How to Download a 7/12 (Satbara) Extract Online in Maharashtra — and 8A vs Property Card
8 min read

How to Check Patta and Chitta Land Records Online in Tamil Nadu (and the EC on TNREGINET)
8 min read

How to Check Adangal and 1B Land Records on Meebhoomi in Andhra Pradesh
8 min read
What Is a Title Search Report? A Developer's Guide to Property Due Diligence in India
14 min read
Automate your due diligence
Skip the manual portal work.
Deedwise automates everything in this article — across every connected portal — and delivers a complete Title Search Report in hours.
Request Access