Role & capabilities
- Search and mapping
- Environmental measurement
- Rescue-support survey
- Primary domain
- Underwater
- System type
- Autonomous underwater vehicle
- Developer / manufacturer
- Rubin Central Design Bureau
- Origin / production countries
- Russia
- Other names
- Junona; Юнона
- Variants / configurations
- Not distinguished in reviewed sources
- Operators / programme customers
- Not identified in reviewed sources
Evidence & current status
Manufacturer reports accumulated use; a named naval customer and current acceptance are not established.
Yunona is Rubin's smaller modular autonomous underwater vehicle for search, mapping and environmental measurements. The manufacturer also identifies support to rescue work as an application. It uses onboard navigation and can be deployed from small vessels or shore facilities, distinguishing it from tether-powered inspection robots.
The published equipment includes side-scan sonar, imaging, inertial and Doppler navigation, acoustic communication and environmental sensors. Rubin offers additional energy and customer-equipment modules, so the base dimensions and endurance should remain attached to the listed configuration. A manufacturer account from 2022 reports more than 1,800 accumulated underwater hours; that is a programme-use total, not the endurance of one deployment.
The record establishes an identifiable Russian survey platform with public technical data. It does not identify a currently accepted naval customer, and search-and-rescue or mapping roles should not be converted into an unsupported combat-service claim. The similarly branded Amulet, Talisman and other Rubin programmes remain separate systems. A future customer record should therefore specify the actual vehicle version and delivery evidence rather than relying on the bureau's broader underwater portfolio.
Sourced specifications
Figures apply to the named configuration. Maximum values are not guaranteed operating performance.
| Specification | Reported value | Context & source |
|---|---|---|
| Configuration | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Hull / propulsion | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Dimensions | 2.90 m long; 200 mm diameter | Published configuration or reported trial baseline; not a guarantee for all variants. Source ↗ |
| Displacement / mass | 87 kg | Published configuration or reported trial baseline; not a guarantee for all variants. Source ↗ |
| Payload | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Endurance | Up to 6 hours | Published configuration or reported trial baseline; not a guarantee for all variants. Source ↗ |
| Range | Up to 30 km at route speed | Published configuration or reported trial baseline; not a guarantee for all variants. Source ↗ |
| Speed | 1.0–1.5 m/s route speed; 3.0 m/s maximum | Published configuration or reported trial baseline; not a guarantee for all variants. Source ↗ |
| Operating depth | 1,000 m | Published configuration or reported trial baseline; not a guarantee for all variants. Source ↗ |
| Sensors | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Communications / control | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Launch / deployment | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
Publication history
- — Added in the September 2026 global coverage review, with sources, configuration limits and explicit data gaps.
Suggest a correction to this entry →
Follow the evidence
Source types identify who makes the claim. Programme milestones and supplier statements should be read in context.