Lakhimpur district
district of Assam, India
Lakhimpur district ( LAK-im-POOR) is an administrative district in the state of Assam, India. The district headquarters is located at North Lakhimpur. It is bounded on the north by the Siang and Papumpare districts of Arunachal Pradesh and on the east by the Dhemaji district and the Subansiri River. Majuli District stands on the southern side and Biswanath District is on the western side .
Etymology
The name Lakhimpur is derived from Lakshmipur, the earlier name of present-day North Lakhimpur. According to the Assam District Gazetteers, the town was named after Lakshminarayana, a Chutia king who ruled in the early fifteenth century. An inscription dated 1401 CE records Lakshminarayana's grant of land to Brahmins on the western bank of the Subansiri River, near present-day North Lakhimpur.
When Lakhimpur district was formed by the East India Company in 1838, the town of Lakhimpur was selected as its first headquarters. Sarbeswar Barua consequently argued that the district took its name from the town, citing an 1839 sanad issued from North Lakhimpur which bears the district seal and an English note of the Principal Assistant Commissioner referring to Lakhimpur district.
History
Lakhimpur figures largely in the annals of Assam as the region where tribes from the east first reached the Brahmaputra.
The public source identifies “Lakhimpur district” as district of Assam, India. This brief keeps that definition visible, then builds a research path around Lakhimpur, district and Assam.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Lakhimpur district”, the useful work is to connect “district of Assam, India” to the records capable of establishing context and consequence.
Place names and jurisdictional language are key evidence: both can reveal earlier catalogue descriptions and overlooked record series. The source revision retrieved here is dated Sep 21, 2026. The linked authority identifier is Q42743. VIAF identifies the subject as 123277277. The Library of Congress control number is n89283889. Authority coordinates are 27.230, 94.100. 4 of 4 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1401, 1838 and 1839.
A single description cannot reconcile every naming convention, rebuilding phase or administrative transfer associated with a place. 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.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Lakhimpur district”, its source revision and the description used here.
- Expand the search: follow Lakhimpur district primary sources, Lakhimpur district archive and Lakhimpur research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Lakhimpur district”?
- Which authority defined the place, boundary or structure at the relevant date?
- Which earlier names or jurisdictions may reveal additional records?
Search terms from this dossier
This entry incorporates text from “Lakhimpur district” 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.