CACrown ArchivesThe cinema collection
Menu
Research dossier · Places & Architecture

Lachhmangarh

tehsil in Alwar district of Rajasthan, India

Architectural plans, a scale model, maps and brass measuring instruments
Places and architectureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionMay 26, 2026
Entity authorityQ123256907
Source-derived summary

Lachhmangarh Assembly constituency was one of the 200 Legislative Assembly constituencies of the Rajasthan Legislative Assembly in India. It was notably represented by Rajendra Singh Gandura, who won the 1998 election by defeating the incumbent Rajasthan government minister, Nasru Khan

. Located in the Alwar district and established in 1962, it stood as one of the largest constituencies in the state before its disestablishment in 2008 following the redrawing of electoral boundaries.

Editorial summary

This brief starts where responsible research should: with the source description of “Lachhmangarh” as tehsil in Alwar district of Rajasthan, India. Everything that follows is an evidence route, not borrowed authority.

Editorial reviewA strong orientation record where physical form, institutional use and historical geography need to be read together. The current lead gives the account dated anchors—1998, 1962, 2008—that can be checked directly. The selected authority fields contribute no independent date. The account is most persuasive where Lachhmangarh, tehsil and Alwar can be independently traced.
Editorial analysis

Why this record matters

The subject matters to the places & architecture register because the source frames it as tehsil in Alwar district of Rajasthan, India. Its deeper value depends on whether names, dates, institutions and citations support that framing.

Evidence profile

The strongest evidence will usually combine a dated visual record with documents produced by the authority responsible for the place. The source revision retrieved here is dated May 26, 2026. The linked authority identifier is Q123256907. Authority coordinates are 28.640, 75.380. None of the 1 selected statements returned an explicit reference. The first chronological checks are 1998, 1962 and 2008.

Critical limits

Architectural summaries often privilege surviving fabric and can understate demolished phases, contested use or displaced communities. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.

Best used for
  • Historic place names
  • Jurisdictional context
  • Routes into maps and plans
Verify next

Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.

Three-step research path

  1. Establish the record: confirm the title “Lachhmangarh”, its source revision and the description used here.
  2. Expand the search: follow Lachhmangarh primary sources, Lachhmangarh archive and Lachhmangarh research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Lachhmangarh”?
  2. Which earlier names or jurisdictions may reveal additional records?
  3. Which authority defined the place, boundary or structure at the relevant date?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from Lachhmangarh” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.