TL;DR
- A Bhoomi RTC (Record of Rights, Tenancy and Crops) is Karnataka's primary land ownership and classification record, maintained by the village accountant and accessible via the Bhoomi portal.
- The RTC has 13 columns — each tells you something different about ownership, land type, current use, and encumbrances.
- An RTC alone is not enough for developer due diligence: it does not show registered charges filed with the Sub-Registrar or undisclosed equitable mortgages.
- Always cross-reference the RTC with the Kaveri Encumbrance Certificate and K-GIS spatial data before any binding commitment.
What a Bhoomi RTC is
The Record of Rights, Tenancy and Crops — universally called the RTC or Pahani in Karnataka — is the government's authoritative record of who owns a piece of land, how much of it, what type of land it is, and who is cultivating it.
It is maintained at the village level by the village accountant (Revenue Inspector) and is updated after every mutation — a formal change in the ownership record following a sale, inheritance, partition, or court order. The Karnataka government digitised these records through the Bhoomi project starting in 1999, making RTC extracts available online via the Bhoomi portal.
For a developer's legal team, the RTC is the starting point for ownership analysis. Every other portal check — Kaveri instruments, K-GIS boundary data, CERSAI charges — is cross-referenced against the ownership picture the RTC establishes.
The 13 columns of an RTC
The Bhoomi RTC is structured as a table with 13 columns. Understanding what each column contains — and what it can and cannot tell you — is essential for any legal team doing Karnataka land due diligence.
Column 1 — Survey number and hissa: The unique identifier for the parcel. A survey number without a hissa suffix is an undivided parcel. A hissa (subdivision) suffix (e.g., 45/2A) indicates the parcel has been partitioned from a larger survey number. Hissa subdivisions require careful tracing — the original survey number's ownership history is the foundation for the subdivided parcel's chain of title.
Column 2 — Extent (area): The total area of the parcel as recorded by the land records department, typically in acres and guntas. This is the official extent — it may differ from GIS-measured area and from the area stated in a sale deed. Discrepancies between Column 2 and K-GIS area should be investigated.
Column 3 — Nature of land (Patta type): Classifies the land as government land (Sarkar), private land (Raiyatwari), or other categories. Only Raiyatwari land can typically be acquired by a private developer. Government land, granted land, or land under the Inam Abolition Act has restrictions on transfer that require specific approvals.
Column 4 — Name of owner (Khatedar): The person(s) recorded as the current owner(s). Multiple names indicate co-ownership. The names here must be cross-referenced with the last registered instrument on Kaveri to confirm the mutation has been updated after every sale. A mismatch between Column 4 and the most recent Kaveri sale deed is a red flag — it could mean the mutation was not done, or that the Bhoomi record has not yet been updated.
Column 5 — Classification of land: Whether the land is wet (irrigated), dry (unirrigated), garden, or homestead. Classification affects conversion requirements and development potential.
Column 6 — Local name of the field (Hissa name): The colloquial or local name of the field, often in Kannada. Used by village accountants to identify the parcel in informal records.
Column 7 — Khatedar's interest (ownership share): The fractional share of each co-owner where the parcel has multiple Khatedars. A parcel with seven co-owners all inheriting from a common ancestor, each with a 1/7th share, requires all seven to execute the sale deed.
Column 8 — Nature of possession (Bhogar): Who is currently in physical possession of the land — the owner, a tenant, or a government leasee. Tenancy rights under the Karnataka Land Reforms Act, 1961 can restrict alienation and in some cases grant the tenant a right to purchase. Any entry indicating a protected tenant is a serious title issue.
Column 9 — Water source: The source of irrigation, if any (canal, well, tank). Relevant for agricultural land valuation but rarely a blocking issue for developer acquisitions.
Column 10 — Nature of trees: Trees of significant value (teak, sandalwood, bamboo) that may be subject to the Karnataka Forest Act or require a tree felling permit before development can begin.
Column 11 — Encumbrances (Saguvali / Revenue encumbrances): This is the most important column for encumbrance analysis at the revenue level. Column 11 records mortgages, attachments, and government dues that have been noted in the revenue records. However, it does not capture encumbrances filed only with the Sub-Registrar (Kaveri) or equitable mortgages filed with CERSAI. A blank Column 11 is not a clean bill of health — it means no charge has been recorded in the revenue system, not that no charge exists.
Column 12 — Government dues: Outstanding land revenue, cess, or other government dues. Unpaid dues create a charge on the property that must be cleared before a transfer can be registered.
Column 13 — Remarks: Free-form notes from the village accountant. Common entries include notices of acquisition proceedings, court orders, survey disputes, and conversion application status. This column requires careful reading — critical information is often buried here in Kannada shorthand.
Why the RTC alone is not enough
The RTC is a revenue record, not a registration record. It reflects what the village accountant has been notified of — it does not automatically capture everything that has happened to the property legally.
Specifically, an RTC will not show:
- Registered charges at the SRO — a mortgage deed executed before a Sub-Registrar creates a charge in the Kaveri database, not automatically in the Bhoomi mutation register. Many mortgages are never reflected in Column 11.
- Equitable mortgages — a loan secured by depositing title deeds with a bank, without a registered deed, does not appear anywhere in Bhoomi. CERSAI is the only official record of these.
- Court attachments in litigation — an attachment order from a district court may take months to reach the village accountant and be entered in the RTC.
- Conversion status — a conversion order from Agricultural to Non-Agricultural (NA) use is issued by the DC's office, not entered automatically in Bhoomi. You need to verify the conversion order separately.
This is why the RTC is the starting point, not the end point, of a Karnataka land title search.
3 common RTC red flags in developer due diligence
1. Mismatch between Column 4 owner and last Kaveri instrument
If the name in Column 4 does not match the last seller in the Kaveri instrument trail, the mutation after the most recent sale has not been completed. This could mean the seller's claim is unregistered, the mutation is pending, or the RTC is stale. In any case, you cannot safely execute a sale deed until the mutation is brought up to date.
2. Government land or grant land in Column 3
Land classified as government-granted (DC Grant, Government Grant, Inam land) has transfer restrictions. Granted land can only be sold after a statutory period (typically 15 years from grant date) and in some cases requires government permission to transfer. Acquiring granted land within the lock-in period is a title defect that cannot be cured by the seller alone.
3. Column 11 encumbrance entry without a corresponding Kaveri release deed
If Column 11 shows an encumbrance entry but there is no registered release deed or discharge in the Kaveri instrument trail to match it, the charge may still be live. The absence of a Kaveri release deed means the mortgage has not been formally discharged at the Sub-Registrar — even if the seller claims it has been settled.
How to cross-reference RTC with Kaveri EC and K-GIS
A robust Karnataka title search requires three sources to be read together:
RTC (Bhoomi) establishes: current owner name, extent, land classification, Column 11 revenue encumbrances, government dues, and tenancy status.
Encumbrance Certificate (Kaveri) establishes: all registered instruments (sale deeds, mortgages, release deeds, gift deeds) in the last 30 years at the specific SRO. The EC is the authoritative record of registered charges. Cross-reference with Column 11: any entry in Column 11 should have a corresponding registration event in the Kaveri EC trail.
K-GIS / KSRSAC establishes: the spatial boundary of the parcel as mapped by the Karnataka Spatial Data Infrastructure. Cross-reference the K-GIS extent with Column 2 of the RTC — discrepancies of more than 5% merit investigation. K-GIS also shows BDA/BBMP reservation zones, road widening proposals, and proximity to notified forests or water bodies.
See our guide to Kaveri Online and Encumbrance Certificates for a detailed walkthrough of how the EC is structured and what it can miss.
From the field — observations from building Deedwise
Automating Bhoomi at scale surfaced a class of data quality issues that simply are not visible when you pull RTCs manually one at a time.
The most frequent operational challenge: mutation lag is longer and more variable than developers assume. We regularly encounter properties where the Kaveri EC clearly shows a registered sale deed from 12 to 18 months ago, but Bhoomi Column 4 still shows the previous owner. The mutation application was submitted, the Kaveri registration happened, but the taluk office has not yet processed the mutation entry. This is not a title defect — it is a bureaucratic lag — but it creates an apparent mismatch that requires investigation before you can confirm the current seller's standing. Flagging this pattern automatically, and distinguishing it from a genuine ownership dispute, is one of the more nuanced parts of the Deedwise pipeline.
The second finding: Column 13 content varies dramatically by taluk. In some taluks, village accountants enter detailed, up-to-date notifications in Column 13. In others, the column is effectively empty even for properties that have pending acquisition proceedings. The lesson: Column 13 is a starting point for red-flag detection, not a definitive clearance. An empty Column 13 does not mean no government action has been taken against a parcel.
The one thing we wish we had known before starting: the Bhoomi portal's survey number search behaviour differs between taluks. Some taluks accept only exact survey number matches; others accept partial matches that can return records for adjacent hissas. Our automation had to be built with taluk-specific search validation to avoid pulling the wrong parcel's records. This is not documented anywhere officially — it took iterating across dozens of taluks in production to map out.
How Deedwise automates Bhoomi
Deedwise's Bhoomi scraper resolves the district, taluk, hobli, and village codes from the submitted property details, then extracts the full RTC using Playwright browser automation against the Bhoomi portal. The raw extract is stored, translated from Kannada where needed using Gemini, and then parsed column by column into structured data.
Column 4 names are extracted and queued for Kaveri cross-referencing. Column 11 entries are parsed and matched against the Kaveri EC instrument trail. Column 13 remarks are translated and scanned for known red-flag patterns (acquisition notices, court orders, conversion pending entries).
The output feeds directly into the ownership and land pillars of the Deedwise Title Search Report, with flags raised wherever the column data conflicts with the Kaveri or K-GIS records.
Frequently asked questions
How current is the Bhoomi RTC data?
Bhoomi data is updated by the village accountant after each mutation is processed. The mutation process itself takes time — from the submission of documents to the final entry can be days to several weeks depending on the taluk. A recently sold property may show the previous owner in Column 4 until the mutation is completed. Deedwise checks the date of the last mutation entry and flags recent changes.
Can I rely on the Bhoomi extract as a certified copy?
The Bhoomi portal issues RTC extracts that are considered certified copies under the Karnataka Land Revenue Act. However, some banks and courts require an RTC certified by the village accountant in person. The Bhoomi extract is legally valid for due diligence purposes.
What is the difference between an RTC and a Pahani?
They are the same document. "Pahani" is the Kannada/Telugu-origin term for the Record of Rights — used colloquially in Karnataka and Andhra Pradesh. The formal Karnataka term is RTC. Bhoomi issues both under the same record structure.
How does Deedwise handle properties with hissa subdivisions?
Deedwise traces the hissa chain — from the original undivided survey number through each subdivision event — to confirm that the partition was properly registered and that the seller's hissa is correctly identified. This involves pulling mutation entries for each subdivision event from the Bhoomi mutation register.
What if the Bhoomi portal is unavailable?
Deedwise retries automatically and notifies the team if the portal is unavailable for more than a defined window. Reports are not closed with silently missing Bhoomi data.
Does a clean RTC mean the property is safe to acquire?
No. A clean RTC means the revenue record shows no obvious encumbrance or dispute. You still need the Kaveri EC and CERSAI check to confirm no registered charges exist, and the eCourts check to confirm no active litigation. A clean RTC is necessary but not sufficient for a clear title opinion.
Continue reading
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