Russian Orthodox Eparchy of Magadan
eparchy of Russian Orthodox Church
The Diocese of Magadan and Sinegorye (Russian: Магаданская и Синегорская епархия) is an eparchy of the Russian Orthodox Church. The Eparchy Cathedral is the Holy Trinity Cathedral in Magadan.
History
The Magadan Diocese was part of the Irkutsk diocese until 1831, when most of it became part of Kamchatka. In 1858, the land was divided into Magadan and the Yakut Kamchatka dioceses, and in 1900, the territory of the latter was transferred to the newly established Diocese of Vladivostok.
In a decision blessed by Patriarch Tikhon on September 11, 1912, the Supreme Church Authority created an independent Department of Kamchatka. The first parish was opened in 1989.
Magadan diocese, which includes Magadan Oblast and Chukotka Autonomous District, was formed by the Holy Synod of the Russian Orthodox Church on February 26,1961.
On July 19, 1999, two further parishes, Anadyr and Chukotka, were added; these are located in the Chukotka Autonomous District.
In 2000, by decision of the Holy Synod of the Russian Orthodox Church, Feofan (Ashurkov) was appointed the new Bishop of Magadan and Sinegorsk. Through his efforts, the first and then subsequent Christmas readings were held with the participation of Alexei Osipov, deacon Andrei Kuraev, and director Nikolai Burlyaev.
The public source identifies “Russian Orthodox Eparchy of Magadan” as eparchy of Russian Orthodox Church. This brief keeps that definition visible, then builds a research path around Russian, Orthodox and Eparchy.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Russian Orthodox Eparchy of Magadan”, the useful work is to connect “eparchy of Russian Orthodox Church” 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 Aug 12, 2026. The linked authority identifier is Q4273872. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1831, 1858, 1900 and 1912.
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 “Russian Orthodox Eparchy of Magadan”, its source revision and the description used here.
- Expand the search: follow Russian Orthodox Eparchy of Magadan primary sources, Russian Orthodox Eparchy of Magadan archive and Russian 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 “Russian Orthodox Eparchy of Magadan”?
- 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 “Russian Orthodox Eparchy of Magadan” 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.