Banglarbhumi registration: how to get the account you need

Start here: you do need an account

Plenty of published advice says otherwise — including, until we corrected it, this page. So let us be exact: a banglarbhumi.gov.in account is required before the portal will give you a land record. Khatian details, plot details, case status: the sign-in comes first.

The wrong version spread so widely because the portal fails late rather than early. Signed out, you can open the lookup screens and the District, Block and Mouza dropdowns will populate one after another exactly as they should. Everything responds; nothing warns you. It is only when you ask for the record itself that the portal replies with its login page instead of a result. Working dropdowns feel like access, and they are not access.

So if you arrived wondering whether registering is worth the bother, the answer is that it is the only route in. The better news is that it is free, takes a few minutes, and one registration covers the whole portal — everything below runs off the same account:

• Know Your Property — search by District, Block and Mouza, then by Khatian number or Plot (Dag) number
• RS-LR Plot Information — plot details across RS and LR records
• Mutation Case Status — where a Dakhil Kharij application has reached
• Conversion Case Status — track a land-conversion application
• Mouza Information — mouza-level details
• Query Search — look up a query you already have a reference for
• Public Grievance — raising a grievance with the department

What an account is actually for

The account does two jobs, and it is worth keeping them apart. It makes record lookups return something instead of redirecting you to sign-in — which is what most people are here for. And it wakes up the transactional menus under Citizen Services, which stay inert behind the message “Please Login and then click Citizen Services” until you are in.

The transactional side is also where charges begin, so the account and the fee are two separate gates rather than one:

• Online Application — Mutation Application, Conversion Application, Warish Application, Land Revenue(Khajna) Application, Mobile Number update Against Khatian, Fees Payment
• Service Delivery — ROR Request, Plot Info. Request, Plot Map Request, Mouza Map Request, Signed ROR/PI/PLM Copy(s), No Due Certificate
• Online Service Status — Mutation Status, Conversion Status, Warish Status, Mutation Plot Khatian Status, Payment Status of Land Revenue (Khajna), Application No. Recovery ( Khajna )
• eChallan Application — eChallan Generation. GRN Search, Mouza Map Availability Details, Application/Report Reprint, RS-LR Information, Land Classification and the Online Fees Calculator are direct Citizen Services entries, not part of this submenu

The mobile number is the most important field on the form

If you take one thing from this page after the section above, take this. The mobile number you register with is not a contact detail — it is the key to the account, and getting it wrong is close to unrecoverable from your sofa.

It carries three jobs at once. It receives the OTP at registration, and it anchors recovery — password reset and Application No. Recovery both depend on it. And it is the anchor for recovery — password reset, and services like Application No. Recovery ( Khajna ) that verify against the registered number.

So the number must be one you personally hold, that is active, and that you expect to keep. Registering with a shop's number, an agent's number, or a relative's handset is the most common way people end up permanently locked out of an account that is nominally theirs. When that number stops being reachable, no amount of retrying will produce an OTP.

What registration asks for

Registration is on the portal's SIGN UP control, in the header beside SIGN IN. The form is short and asks for ordinary account details rather than land documents — you are creating a user, not filing anything about a plot.

Expect to provide, broadly: your name, a mobile number, an email address, a chosen user ID and password, address details, and a CAPTCHA. The mobile number is then verified by OTP. Exact fields shift as the portal is updated, so treat this as the shape rather than a checklist.

One thing it is not: registration does not attach a Khatian to your account. The account is a login, nothing more — it does not assert that you own anything, and each application separately identifies whatever holding it concerns. Having an account is what lets you *search* the records; it says nothing about whose name is in them.

• Enter your name as you would want it to appear on an application, and be consistent across services.
• Use an email address you can actually open — some reset routes go there rather than to SMS.
• Choose a user ID you can reproduce exactly. It is case-sensitive at sign-in.
• Keep the password somewhere retrievable. Reset depends on the registered mobile or email working.

Why registration fails, and what each failure means

Sign-up failures cluster into a handful of causes, and the portal's error messages rarely distinguish between them.

• The OTP doesn't arrive. Wait several minutes before requesting another — on many portals a fresh request invalidates the previous code, so repeated tapping can leave you with nothing usable. Turn off SMS-filtering apps, check the blocked or spam folder, and confirm the handset's message storage isn't full.
• The CAPTCHA keeps failing. Refresh it rather than guessing at an ambiguous character. Some screens report a wrong CAPTCHA as a different error entirely, which sends people off fixing the wrong thing.
• “User already exists”. Someone — often an agent or a relative who once helped — may have registered against your number or email already. Try password recovery on that identifier before creating anything new.
• The page hangs or errors before you can submit. That is portal availability, not your details. Try again at a quieter time; there is nothing to fix on your side.
• Auto-capitalisation. Mobile keyboards capitalise the first character of an empty field, which quietly changes a user ID or email you thought you typed correctly. Check it character by character before submitting.

After registering — and where the portal can't help

Once the account exists, signing in needs the user ID, the password and the CAPTCHA. If sign-in itself becomes the problem, that has its own set of causes and fixes worth reading separately.

If your mobile number changes later, the portal carries Mobile Number update Against Khatian under Online Application — but note it sits *behind* the login, so it only helps while you can still get in. If you are already locked out because the old number is gone, the route is your local BL&LRO office, not the website.

And an account solves none of the substantive problems. If the record shows the wrong name or area, if an inheritance was never recorded, or if ownership is contested, registering changes nothing — those go to the BL&LRO office, and where a dispute or money is involved, to an advocate. We are not able to advise on any of that.

One app note, ours: Bhumir Tathya is an unofficial Android app we build at Devikon — free and bilingual, presenting the portal's lookups as native screens. It signs in with your own banglarbhumi.gov.in account, so it needs you to have one: it does not create accounts for you, and no third-party app bypasses government authentication. It also keeps records you have already opened readable offline, though a saved copy shows the record as it stood when you viewed it and should be re-checked on the portal before you rely on it.