RosUkrEnergo
company

RosUkrEnergo is a Swiss-registered venture company that transports natural gas from Turkmenistan to East European countries. 50% of the company is owned by Gazprom, through its subsidiary Swiss-registered Rosgas Holding A.G., and another 50% by Swiss-registered private company Centragas Holding A.G., acting on behalf of a consortium of GDF Group owned by Dmytro Firtash and Ivan Fursin.
Before the 2009 Russia–Ukraine gas dispute, it was the sole importer of natural gas from Gazprom, reselling it to Naftogaz Ukrainy. Critics have questioned Gazprom's claimed need for RUE as a middleman. RUE has been accused of simply being “a corrupt intermediary” but has dismissed suggestions that Russian or Ukrainian politicians benefit from the arrangement.
History
The company was created in July 2004 in a deal by former Ukrainian President Leonid Kuchma and his Russian counterpart Vladimir Putin to replace Eural Trans Gas. Until 2006 the company acted as a middleman between Turkmenistan and Ukraine. The company also sells Turkmenistan gas to Poland. Due to an agreement between Gazprom and Naftogaz, from 2006 till January 2009 the company supplied all of Ukraine's natural gas imports from Russia and other Central Asian countries, in addition to Turkmenistan and Uzbekistan. On October 24, 2008 Gazprom and Ukraine's national energy company Naftogaz signed a long-term cooperation deal in which was stated that Ukraine will receive Russian natural gas directly from Gazprom and Naftogaz will be the sole importer of Russian natural gas.
“RosUkrEnergo” enters the record as company. Crown Archives preserves that source wording while asking what RosUkrEnergo and company can confirm, complicate or overturn.
Why this record matters
“RosUkrEnergo” is worth following because a concise public description often conceals a longer documentary argument. Here, RosUkrEnergo and company provides the most credible route into that argument.
Contemporary correspondence, administrative files and participant testimony can test how later narratives organized the event or institution. The source revision retrieved here is dated Oct 8, 2025. The linked authority identifier is Q673771. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2009, 2004, 2006 and 2008.
Official terminology may obscure informal participation, dissent or communities documented only indirectly. 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
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “RosUkrEnergo”, its source revision and the description used here.
- Expand the search: follow RosUkrEnergo primary sources, RosUkrEnergo archive and RosUkrEnergo 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 “RosUkrEnergo”?
- Which voices are present, absent or mediated by the institution?
- What chronology connects this entry to wider political or social change?
Search terms from this dossier
This entry incorporates text from “RosUkrEnergo” 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.