Cristuru Secuiesc
town in Harghita County, Romania
Cristuru Secuiesc (Romanian pronunciation: [ˌkristuru sekuˈjesk]; Hungarian: Székelykeresztúr, pronounced [ˈseːkɛjkɛrɛstuːr] ) is a town in Harghita County, Romania. It lies in the Székely Land, an ethno-cultural region in eastern Transylvania. The town administers two villages: Betești (Betfalva), part of Mugeni until 2004, and Filiaș (Fiatfalva).
Location
Cristuru Secuiesc lies on the Transylvanian Plateau, in the area where the river Goagiu flows into the Târnava Mare. It is located in the southwestern part of the county, on the border with Mureș County. The town is crossed by national road DN13C; Odorheiu Secuiesc is 26 km (16 mi) to the east, while the county seat, Miercurea Ciuc, is 78 km (48 mi) in that direction.
History
The town was part of the Székely Land area of the historical Transylvania province. It belonged to Udvarhelyszék until the administrative reform of Transylvania in 1876, when it fell within the Udvarhely County of the Kingdom of Hungary. In the aftermath of World War I and the Hungarian–Romanian War of 1918–1919, it passed under Romanian administration; after the Treaty of Trianon of 1920, like the rest of Transylvania, it became part of the Kingdom of Romania. During the interwar period, the town fell within Odorhei County.
Begin with the source’s own compact description: “Cristuru Secuiesc” is town in Harghita County, Romania. The dossier treats that line as a proposition to test through Cristuru, Secuiesc and town, not as a finished interpretation.
Why this record matters
The phrase “town in Harghita County, Romania” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
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 19, 2026. The linked authority identifier is Q851056. VIAF identifies the subject as 159523994. The Library of Congress control number is n85375345. Authority coordinates are 46.292, 25.035. 4 of 5 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2004, 1876, 1918 and 1919.
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.
- 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 “Cristuru Secuiesc”, its source revision and the description used here.
- Expand the search: follow Cristuru Secuiesc primary sources, Cristuru Secuiesc archive and Cristuru 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 “Cristuru Secuiesc”?
- Which authority defined the place, boundary or structure at the relevant date?
- What physical evidence or contemporary plan supports the description?
Search terms from this dossier
This entry incorporates text from “Cristuru Secuiesc” 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.