Güləbird
village in the Lachin District of Azerbaijan
Güləbird (Gulabird) or Tsaghkaberd (Armenian: Ծաղկաբերդ, lit. 'castle of flowers') is a village in the Lachin District of Azerbaijan.
History
Gulabird, then called Kulaberd in Armenian (Armenian: Կուլաբերդ), was the easternmost fortification of the Armenian Principality of Kapan (1722–1730) formed by the commander Davit Bek following the Syunik Rebellion, it is also where the modern-day village gets its name.
The village was located in the Armenian-occupied territories surrounding Nagorno-Karabakh, coming under the control of ethnic Armenian forces in August 1993 during the First Nagorno-Karabakh War. The village subsequently became part of the breakaway Republic of Artsakh as part of its Kashatagh Province, referred to as Tsaghkaberd (Armenian: Ծաղկաբերդ, lit. 'castle of flowers'). It was seized by Azerbaijan on 9 November 2020 during the Lachin offensive in the 2020 Nagorno-Karabakh war.
Economy
After returning to Azerbaijan control, the Gulabird hydroelectric power plant was declared reopened in 2021. It is a small 8 MW power plant.
Historical heritage sites
Historical heritage sites in and around the village include a cave, the 12th/13th-century rock-cut church of Kronk (Armenian: Քրոնք), and the 17th/18th-century bridge of Kotrats (Armenian: Կոտրած).
Demographics
The village had 271 inhabitants in 2005, and 221 inhabitants in 2015.
See also
List of power stations in Azerbaijan
References
Bibliography
Ayvazyan, Armen (2006).
The public source identifies “Güləbird” as village in the Lachin District of Azerbaijan. This brief keeps that definition visible, then builds a research path around Güləbird, village and Lachin.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Güləbird”, the useful work is to connect “village in the Lachin District of Azerbaijan” to the records capable of establishing context and consequence.
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 Sep 21, 2026. The linked authority identifier is Q4791294. Authority coordinates are 39.483, 46.610. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1722, 1730, 1993 and 2020.
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 “Güləbird”, its source revision and the description used here.
- Expand the search: follow Güləbird primary sources, Güləbird archive and Güləbird 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 “Güləbird”?
- What physical evidence or contemporary plan supports the description?
- Which earlier names or jurisdictions may reveal additional records?
Search terms from this dossier
This entry incorporates text from “Güləbird” 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.