Parliamentary constituencies · boundary file read 2026-09-29
Tezpur — parliamentary constituency no. 9, Assam
This page is about the seat, not about whoever holds it. The seat is the part that outlasts an election: a member can be replaced and the record of the seat remains, which is the opposite of how our table is built — it holds one row per person and no history at all.
The boundary file flags this feature “Pre delimitation” in its own attributes. It describes the seat before the most recent delimitation, so its extent is not the extent of the seat contested at the last election. 39 of the 543 features in this layer carry that flag.
What the boundary file says about this seat
Every value below is the source file’s own, shown as it is stored. Nothing is translated, expanded or modernised.
- Seat name in the file
- Tezpur
- Name in Devanagari
- तेजपुर
- State in the file
- Assam
- Constituency number in the source file
- 9
- Join key in the file
- pc_id 1809
- Category code in the file
- GEN — the file carries this code with no key explaining it, so we show the code and do not expand it.
- Delimitation flag in the file
- “Pre delimitation”
- Vintage the file claims for itself
- 2019 delimitation as scraped by DataMeet; not re-verified against any 2024 notification
- Wikidata item in the file
- Q1606703
Who our record names on this seat
No row in our table names this seat in this state. That is a statement about our table rather than about the seat. Measured on 2026-10-02: of the 543 seats in this layer, 489 match at least one Lok Sabha row whose stored state agrees with the file, 29 match a row that names the seat but spells the state differently, and 25 match nothing; in the other direction, 26 of our 551 Lok Sabha rows name a seat this file does not contain under any spelling. All 14 of the file's Assam features carry its own "Pre delimitation" flag and the older names that go with it, which is one way a sitting member and a real seat can fail to meet. So this seat may well have a member in our table, filed under a spelling this file does not use.
The member directory is searchable by name and by seat, and is the place to look for a member this page could not reach.
What this tier can and cannot do
This is a property of the seat rather than of its holder, which is why it belongs on this page and survives the holder. It is the same block the record pages show, with the same citations.
Member of Parliament, Lok Sabha
Researched and citedApplies to all of India · answers for one parliamentary constituency
What this seat can do
Recommend works in the constituency up to ₹5 crore a year under MPLADS; the District Authority may sanction up to the full entitlement.
Expect a decision on time: recommended eligible works should be sanctioned within 75 days, and any rejection told to the MP within 45 days with reasons.
Sit as an ex-officio member of the GMDA Authority, where the parliamentary constituency falls inside GMDA's notified area. The Authority is chaired by the Chief Minister of Haryana.
Choose which district in the constituency acts as the nodal district for MPLADS.
What this seat cannot do
Sanction, tender or execute anything. The MP recommends; the District Authority sanctions and gets the work executed through an implementing agency it selects.
Recommend renovation or repair work, as the guidelines stood in June 2016 — prohibited, with a narrow exception for retrofitting essential lifeline buildings such as government hospitals and schools. Whether the April 2023 revision still bars it we could not check: that edition is published only on mplads.gov.in, which does not answer from our network, and reporting says repair became permissible after a reasonable gap since the original construction.
Our reading of the cited provision, not something the source states
Recommend revenue or recurring expenditure. The scheme builds things; it does not run them. Nor may it acquire land, reimburse work already done, or name an asset after anyone.
Change the work or the site once the work has begun and expenditure liability has been incurred.
Recommend through a staffer or an intermediary. Recommendations from third parties and from an MP's representatives are inadmissible and cannot be acted on.
The money attached to the seat
₹5 crore per year
Members of Parliament Local Area Development Scheme (MPLADS)
one legislator's annual scheme ceiling
The most this member may recommend in a year under one scheme. It is a ceiling on recommendations, not a measure of what was built and not money the member spends. Spent by the District Authority — the District Collector, District Magistrate or Deputy Commissioner — which sanctions the works the MP recommends.
What we still do not know about this tier
- How much of the entitlement was actually recommended, sanctioned, released or spent. mplads.gov.in does not answer from our network and no export has been verified to exist, so we show nothing — not a zero and not a dash.
- The paragraph numbers cited come from the June 2016 edition of the guidelines. MoSPI revised them with effect from 1 April 2023 and we could not read the revised text; the amounts are restated in 2025 Haryana publications, but locators may have moved.
MPLADS is a central scheme, so this holds in every state. The GMDA seat holds only for constituencies inside GMDA's notified area.
Reports inside this boundary
Held back during the election period
Nobody has recorded a check of the Election Commission's announcements, so this site does not know whether an election period is running. Unknown is treated as "in force". Comparative, aggregate and preference-shaped content about candidates is held back while that is the case, because publishing it inside a notified period can carry a prison term under the Representation of the People Act, 1951. Individual record pages, office contact details and the whole reporting and escalation loop are unaffected.
Counting residents’ reports per constituency is one of the surfaces this site freezes during an election period, so the page asks for permission rather than deciding for itself. The check was made at 2026-10-02T13:28:22.149Z. Every individual report stays open and visible on the map; what is held back is the per-seat total.
What this page cannot show you
There is no list of past holders here, and that is not an omission we can fill by writing one. Our `representatives` table has one row per person and no history: no table of terms, no row for a member who has left, and a start date recorded for nobody. The only history it has ever held is six rows marked not current, added after a person researched six members and found them out of their seats — which is the end of a term recorded without the term. So this page can tell you what our record says about the seat today and what it cannot vouch for; it cannot tell you who held the seat before, because the database has never held a departed member's term. A seat page is the surface that makes that gap obvious rather than invisible, and the fix is a holders table with sourced, dated terms — not a guess assembled from the row that happens to be here.
Counted on this request: 571 rows in the table, 0 with a start date, 4 with an end date, 0 marked current, 6 marked not current, and 565 saying nothing either way.
The boundary file’s own list of what is wrong with it
- 39 of 543 features carry source_status "Pre delimitation" and pre_delimitation true (Assam 14, Jharkhand 14, Jammu & Kashmir 6, Arunachal Pradesh 2, Manipur 2, Nagaland 1). Their geometry does not describe the seat contested in 2024. Label or exclude them; do not present them as current.
- pc_no 30 in Maharashtra (st_code 13) was labelled "Mumbai South" in the source, duplicating pc_no 31 and omitting Mumbai South Central. Renamed here to "Mumbai South Central" with wikidata_qid Q6935325; the change is recorded on that feature under name_corrected.
- Join on pc_id, or on st_code + pc_no. Never on pc_name: roughly 22 seats differ in spelling from other Indian sources.
- Coordinate precision in the source is 3 decimal places (about 110 m). Boundaries are indicative, not survey-grade. A point within about 100 m of a boundary may resolve to the neighbouring seat.
Those are the file’s words, not ours. This is the join the file itself tells us not to make. Its own defect list says: "Join on pc_id, or on st_code + pc_no. Never on pc_name: roughly 22 seats differ in spelling from other Indian sources." Our rows carry no constituency id of any kind — no pc_id, no seat number, nothing that points at a boundary feature — so the seat name and the state as text is the only join available.