Rusnano
Russian government owned company
Rusnano Group (Russian: Роснано АО, lit. 'Rosnano plc.') is a Russian state-established and funded company. The Rusnano Group's mission is to create competitive nanotechnology-based industry in Russia. Rusnano invests directly and through indirect funds into all major knowledge-based areas where nanotechnology is widely implemented: electronics, optics, telecom, classic and renewable energy, healthcare and biotechnology, materials and metallurgy, engineering and chemistry.
History
In April 2007 the Russian President Vladimir Putin has announced an Initiative termed «Strategy for Development of Nanotechnology Industry» in which he outlined the goals of new Russian policy on nanotechnology industry.
The Group was founded in 2011 by reorganizing Russian Corporation of Nanotechnology, into RUSNANO JSC, RUSNANO Management Company LLC and a non-profit Fund for Infrastructure and Educational Programs (FIEP). These separate legal entities work together on increasing competitiveness and effectiveness of Russian companies in nanotechnology-related industrial fields.
In 2015 Rusnano had 16 investment projects, including investments into about 97 plants and R&D companies in 37 regions of Russia. In 2016 many such enterprises were either dissolved, bankrupted or repurposed. In 2016 the company was on the verge of bankruptcy significantly devaluating below the equity levels but managed to recover. As of 2017, 100% shares of Rusnano were owned by the Russian government.
This brief starts where responsible research should: with the source description of “Rusnano” as russian government owned company. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the history & society register because the source frames it as russian government owned company. Its deeper value depends on whether names, dates, institutions and citations support that framing.
The record creator and administrative purpose are central evidence, because official documentation reflects both action and institutional priorities. The source revision retrieved here is dated Sep 10, 2026. The linked authority identifier is Q2279155. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2007, 2011, 2015 and 2016.
Institutional narratives can privilege the records that survived while minimizing voices that were never formally collected. 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 “Rusnano”, its source revision and the description used here.
- Expand the search: follow Rusnano primary sources, Rusnano archive and Rusnano 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 “Rusnano”?
- Which voices are present, absent or mediated by the institution?
- Who created the surviving record, and for what administrative purpose?
Search terms from this dossier
This entry incorporates text from “Rusnano” 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.