Role & capabilities
- Proposed reconnaissance role
- Proposed cargo carriage
- Primary domain
- Underwater
- System type
- Autonomous underwater vehicle
- Developer / manufacturer
- A.M.M.O. Ukraine
- Origin / production countries
- Ukraine
- Other names
- Марічка; Maritchka
- Variants / configurations
- Not distinguished in reviewed sources
- Operators / programme customers
- Not identified in reviewed sources
Evidence & current status
Project-owner evidence supports identity and prototype activity. Range is a developer claim; acceptance, production and operational employment remain unverified.
Marichka is an underwater-vehicle project associated with the A.M.M.O. Ukraine foundation and engineering team. The organisation's own pages identify the project, show a prototype and describe buoyancy and early testing. This is a firmer basis for programme identity than anonymous reposted imagery, while still falling short of a government acceptance record.
The project page promotes several potential roles, including reconnaissance and cargo carriage, alongside its military purpose. It also advertises a range exceeding 1,000 kilometres. This figure is retained as the developer's claim, with no implication that a complete mission at that distance has been independently demonstrated. The reviewed pages do not provide a dated, comprehensive specification covering depth, energy, speed, mass and sensor configuration.
Marichka is therefore listed as a development programme. Its published material does not establish production quantity, naval unit assignment or combat use. It is kept separate from the Toloka family, whose model identities and public configuration claims need their own verification. The catalogue describes the vehicle and the evidence behind its maturity, without reproducing proposed attack procedures or construction details.
Sourced specifications
Figures apply to the named configuration. Maximum values are not guaranteed operating performance.
| Specification | Reported value | Context & source |
|---|---|---|
| Configuration | Uncrewed underwater development vehicle | Published configuration or reported trial baseline; not a guarantee for all variants. Source ↗ |
| Hull / propulsion | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Dimensions | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Displacement / mass | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Payload | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Endurance | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Range | Developer advertises over 1,000 km | Unverified design claim; no complete-distance trial established in the reviewed primary evidence. Source ↗ |
| Speed | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Operating depth | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. 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.