R-360 Neptune
Ukrainian anti-ship cruise missile

The R-360 Neptune (Ukrainian: Р-360 «Нептун», romanized: R-360 "Neptun") is a Ukrainian family of subsonic cruise missiles with all-weather capabilities developed by the Luch Design Bureau in Kyiv as an anti-ship missile, with a later variant for land attack. Neptune's design is based on the Soviet Kh-35 subsonic anti-ship missile, with substantially improved range, targeting and electronics equipment. It has a range of over 200 kilometres.
The system requirement was for a single missile to defeat surface warships and transport vessels with a displacement of up to 9,000 tonnes, either in convoys or moving individually. The first training missile divizion (battalion) entered service with the Ukrainian Navy in March 2021, with the first operational naval use in 2022. The land-attack variant has a new guidance system and was first fielded and used in 2023. "Long Neptune", an extended range land-attack variant with a claimed 1,000 km range, was first used in 2025, according to Ukrainian president Volodymyr Zelenskyy.
Development
The missile was first revealed at the 2015 Arms and Security international exhibition in Kyiv.
According to information from open sources, the first flight examples of the cruise missile were manufactured in the second quarter of 2016. Production of advanced missile systems took place in cooperation with other Ukrainian companies, including Artem Luch, Motor Sich (MS400 turbofan engine), ZhMZ Vizar Kyiv, Radionix (seeker) and Arsenal SDP SE (navigation system).
This brief starts where responsible research should: with the source description of “R-360 Neptune” as ukrainian anti-ship cruise missile. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as ukrainian anti-ship cruise missile. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Sep 27, 2026. The linked authority identifier is Q28706540. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2021, 2022, 2023 and 2025.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. 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
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “R-360 Neptune”, its source revision and the description used here.
- Expand the search: follow R-360 Neptune primary sources, R-360 Neptune archive and R-360 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 “R-360 Neptune”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “R-360 Neptune” 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.