Ozun
commune in Covasna County, Romania
Ozun (Hungarian: Uzon, Hungarian pronunciation: [ˈuzon]; German: Usendorf) is a commune in Covasna County, Transylvania, Romania composed of seven villages: Bicfalău (Bikfalva), Lisnău (Lisznyó), Lisnău-Vale (Lisznyópatak), Lunca Ozunului (Vesszőstelep), Măgheruș (Sepsimagyarós), Ozun, and Sântionlunca (Szentivánlaborfalva).
Demographics
The commune has an absolute Székely Hungarian majority. According to the 2011 census, it had a population of 4,430 of which 82.71% or 3,664 were Hungarians, 11.6% or 514 were Romanians, 2.93% or 130 were Roma, and 0.11% or 5 were part of another ethnic group. At the 2021 census, Ozun had a population of 4,213, of which 79.47% were Hungarians, 12.58% Romanians, and 1.02% Roma.
History
The settlement formed part of the Székely Land region of the historical Transylvania province. Until 1918, the village belonged to the Háromszék County of the Kingdom of Hungary. In the immediate aftermath of World War I, following the declaration of the Union of Transylvania with Romania, the area passed under Romanian administration during the Hungarian–Romanian War of 1918–1919. By the terms of the Treaty of Trianon of 1920, it became part of the Kingdom of Romania.
In 1925, the commune fell within Plasa Ozun of Trei Scaune County. In August 1940, under the auspices of Nazi Germany, which imposed the Second Vienna Award, Hungary retook the territory of Northern Transylvania (which included Ozun) from Romania.
This brief starts where responsible research should: with the source description of “Ozun” as commune in Covasna County, Romania. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the places & architecture register because the source frames it as commune in Covasna County, Romania. Its deeper value depends on whether names, dates, institutions and citations support that framing.
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 Oct 27, 2024. The linked authority identifier is Q16426328. Authority coordinates are 45.791, 25.889. 1 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2011, 2021, 1918 and 1919.
Modern boundaries and familiar names can conceal earlier jurisdictions or structures that do not align with the present site. 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 “Ozun”, its source revision and the description used here.
- Expand the search: follow Ozun primary sources, Ozun archive and Ozun 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 “Ozun”?
- 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 “Ozun” 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.