The Missile That Came In from the Cold
Debris, Desk Models, and the Soviet Lineage of Oreshnik.
Since its first combat use in 2024, Russia’s Oreshnik intermediate-range ballistic missile (IRBM) has attracted considerable public attention. While most analysis has focused on the system’s implications for nuclear and conventional deterrence, far less attention has been paid to the missile’s technical characteristics.
This is largely a result of Russian operational security. Unlike many other Russian missile systems, whose imagery is regularly leveraged for strategic messaging, Oreshnik has so far remained in the shadows. Russia has neither displayed the missile itself nor its launcher.
Open sources nevertheless provide a basis for a preliminary technical assessment. Available evidence does offer important clues about the missile’s post-boost vehicle (PBV) and transporter-erector-launcher (TEL). A reconstruction of the latter, in turn, allows for new insights into the missile itself, suggesting it is derived from the second and third stages of the Yars intercontinental ballistic missile (ICBM). This would make Oreshnik a conceptual heir to the little-known late-Soviet Skorost program.
Return of Rubezh
With Russia largely withholding information about Oreshnik, key details about the system have instead come from outside the country. In November 2024, shortly after its first combat use, the Pentagon described Oreshnik as an experimental IRBM derived from Russia’s controversial RS-26 Rubezh missile.
Developed by the Moscow Institute of Thermal Technology (MIT) and first successfully tested in 2012, Rubezh was presented by Russia as a new solid-propellant ICBM capable of carrying multiple independently targetable reentry vehicles (MIRVs) and of overcoming advanced Western missile defenses. Western governments and analysts challenged this characterization, arguing that with a realistic payload the missile would be more accurately described as an IRBM and therefore violate the INF Treaty. In 2018, Moscow eventually announced that it had defunded the program. The US intelligence community, however, maintained that Russia continued testing of equipment associated with Rubezh after 2018.
Although Russia never released imagery of Rubezh, it was somewhat more forthcoming about the system’s technical characteristics than it has been about Oreshnik. In 2013, Russian state media, citing comments by Sergei Karakaev, commander of the Strategic Rocket Forces (RVSN), reported that the missile had been ‘created on the basis of the RS-24 Yars’ ICBM, while being significantly lighter than Yars. The US government repeated Karakayev’s claim that the system was based on Yars. Footage released in 2026 of an Oreshnik forward deployment site in Belarus showed support vehicles identical to those used by Yars units, further strengthening the case for a common lineage linking Oreshnik, Rubezh and Yars.
Reading the debris
The first concrete open-source evidence of Oreshnik’s wider architecture came from debris recovered after its combat use in Ukraine. Imagery released by Ukrainian government and media channels shows a number of parts all associated with the system’s post-boost vehicle (PBV).
Among these are the remnants of the post-boost control system, which orients and steers the PBV outside the atmosphere. Unlike US land-based ICBMs, which use liquid-propellant thrusters, Oreshnik appears to employ a continuously operating solid-propellant gas generator feeding a set of valve-controlled thrusters. A range of MIT patents relating to hot gas valves and solid-propellant post-boost control systems as well as footage of similar valve mechanisms being assembled at the Votkinsk Machine Building Plant suggest that this may be a more common feature of missiles designed by the Institute.
Another component recovered after several Oreshnik strikes is the sealed instrumentation compartment that houses the missile’s navigation and guidance systems and is likely installed on top of the post-boost control system. The compartment can be identified by its close structural resemblance to the equivalent design used in the RT-2PM Topol-derived START-1 space-launch vehicle. On at least one occasion, the relatively intact state of the compartment allowed Ukrainian investigators to recover the missile’s gyro-stabilized platform, a key component of the guidance system.
Payload ambiguity
Judging from the design of other MIT-developed missile systems, the individual reentry vehicles would likely be mounted on a frame attached to the top of the instrumentation compartment. Yet of all the elements of Oreshnik, its actual payload is the least understood. It remains unknown how many MIRVs the missile carries in its nuclear configuration. In its conventional configuration, footage of strikes in Ukraine showed 36 glowing objects descending in six clusters. This pattern could be explained in several ways: 36 reentry vehicles released exo-atmospherically in batches of six; six non-survivable reentry vehicles, each releasing six unguided submunitions endo-atmospherically, or six survivable reentry vehicles each releasing five submunitions and remaining visible alongside the submunitions.
The reconstructions of the post-boost control system and the missile itself, however, indicate that such a large number of submunitions would face severe volumetric constraints. Assuming a configuration of six reentry vehicles, each releasing six submunitions, the maximum diameter of each submunition would be only around 10–13 cm. If reports that Russia used non-explosive effectors are accurate, this may therefore not indicate the use of dummy warheads as sometimes alleged but rather reflect a deliberate choice of kinetic effectors as one of the few payload types compatible with such dense packaging.
Clues from Minsk
The most significant open-source evidence on Oreshnik emerged from a rather unlikely source: Aleksandr Lukashenko’s TV desk. In late 2025, a small scale model of the missile’s transporter-erector-launcher (TEL) appeared in the Belarusian president’s office, where it has since been visible in various photographs of official meetings.
The chassis’ six-axle configuration, wheel spacing and cab layout allow it to be identified as the Belarusian MZKT-79291 which had previously been suggested as the likely platform for the Rubezh TEL. Separately, a 2011 patent filed by Russia’s principal TEL manufacturer, Titan-Barrikady, included drawings of an unidentified TEL for a large-diameter missile based on the same MZKT vehicle family.
Known dimensions of the MZKT-79291, including its cab and Belshina Bel-155 tyres, together with extensive available imagery of the chassis, allow for a reasonably dimensionally accurate 3D reconstruction of the vehicle. When combined with the Titan-Barrikady patent and the scale model displayed in Lukashenko’s office, this provides the basis for a preliminary reconstruction of the Oreshnik TEL.
The chassis itself matches a vehicle visible in open storage on satellite imagery of Titan-Barrikady’s Volgograd facility. The dimensions and layout of the reconstructed Oreshnik TEL also closely correspond to a possible Rubezh TEL identified by satellite-imagery analyst Ben Reuter at the Kapustin Yar test range in 2016.
Most significantly, the TEL reconstruction makes it possible to estimate the diameter and length of the missile canister, and to compare these with possible Yars-derived configurations. This comparison indicates that the frequently repeated claim that Oreshnik replicates the RSD-10 Pioneer model, using the first two stages of the Yars ICBM just as Pioneer used the first two stages of the Temp-2S ICBM, is not credible. Even allowing for substantial measurement error, the TEL and launch canister are too short to accommodate a Yars first- and second-stage derivative.
The canister length would, however, be consistent with a missile derived either from the first stage of the Yars or from a combination of its second and third stages. The launch canister on the observed TEL appears smaller than that used for Yars. Combined with the fact that two-stage configurations are the more conventional architecture for solid-propellant IRBMs, this makes a derivative based on the Yars’ second and third stages the more plausible configuration.
Soviet precedents
Should Rubezh/Oreshnik prove to have been derived from the second and third stages of the Yars, it would point to the revival of an earlier Soviet concept: the little-known 15Zh66 Skorost (Speed) missile.
Development of the Skorost began in 1983, after NATO started deploying Pershing II ballistic missiles and ground-launched Tomahawk cruise missiles in Europe. The Pershing II’s short flight time caused particular concern in Moscow, prompting Soviet interest in a rapid-reaction system that could be forward deployed in Warsaw Pact countries and hold key NATO targets in Europe at risk. Unusually for a Soviet IRBM, Skorost was reportedly intended for allocation to both the RVSN and the Soviet Ground Forces. Like Oreshnik, it was also envisaged in both MIRVed nuclear and conventional configurations.
To meet the compressed development timeline set by the Soviet leadership, MIT drew on elements of existing missile systems. The second stage of the RT-2PM Topol ICBM was adapted as Skorost’s first stage, while Topol’s third stage became Skorost’s second. The post-boost vehicle was derived from the Pioneer.
The missile underwent only one flight test, in 1985, which ended in failure. As the country’s political outlook changed under Gorbachev, any further testing was halted. The program was eventually cancelled after the signing of the INF Treaty in 1987.
But while Skorost was largely forgotten in the West, it appears to have remained present in Russian thinking. In 2005, when Moscow briefly considered withdrawing from the INF Treaty, a Russian military source quoted by Interfax identified two possible routes for developing new INF-range missiles: an extended-range Iskander variant, or an IRBM drawing on “the achievements in research and technology gained in the development of the Skorost missile system in the 1980s.”
It seems likely that Russia ultimately followed this path, reviving the Skorost concept of building a dual-capable IRBM around the second and third stages of an existing ICBM, this time using the more capable Yars as the basis.
Novel weapons, old legacies
Russian officials, including President Vladimir Putin, have repeatedly presented the country’s ‘novel weapons’, designed to overcome or bypass Western missile defenses, as a break with the past. Rather than repeating the Soviet pattern of technological catch-up and economically ruinous numerical parity, Moscow would leap ahead through advanced technologies enabling an asymmetric response to the West.
On closer inspection, however, many of Russia’s novel weapons seem to remain deeply rooted in Soviet ideas, concepts and technologies. Sarmat fills the same heavy-ICBM niche as its predecessor, the R-36M2 Voevoda, and appears to continue the fractional orbital-bombardment system concept (FOBS) the Soviet Union had already operationalized in the 1960s. Kinzhal is an air-launched derivative of the Iskander, whose development was already initiated under Gorbachev. Poseidon reflects an old Soviet interest in undersea nuclear delivery systems, while Avangard appears to have evolved from the Albatros project. Oreshnik, as argued above, seems to fit the same pattern.
Russia’s deep-strike systems appear to be developing along increasingly divergent lines. Its rapidly evolving drone capabilities have few connections to the country’s past, drawing instead on Iranian designs, Chinese commercial off-the-shelf components and rapid battlefield adaptation. In the missile domain, however, Soviet legacies continue to shape the development paths Moscow follows and the strategic options it pursues.











A highly interesting piece - thanks! I became a subscriber...
I am NOT suggesting that it would be the case right here, but already during the Soviet times, they muddled the waters by planting fake 'evidence' to be 'found' by Western analysts. Hence I feel a tad cautious about the miniature TEL behind the Dictator.
Really interesting analysis, thanks!