Role & capabilities
- Cargo transport
- Casualty evacuation configuration
- Primary domain
- Land
- System type
- Ground logistics vehicle
- Developer / manufacturer
- Ratel Robotics
- Origin / production countries
- Ukraine
- Other names
- No additional names recorded
- Variants / configurations
- Not distinguished in reviewed sources
- Operators / programme customers
- Not identified in reviewed sources
Evidence & current status
Payload wording is inconsistent; no definitive payload rating inferred from the mass difference. No Ratel H operator evidence transferred to Ratel M.
Ratel M is Ratel Robotics' logistics and casualty-evacuation platform. Its manufacturer presents it as a separate model alongside Ratel H, with its own dimensions, mass and travel-range figures. The principal role is carrying supplies or a stretcher-equipped evacuation package, rather than a permanently installed armed mission module.
The listed system includes the vehicle, ground control station, charging equipment and communications components. A satellite-based control option is also described. These items establish a remotely operated system; the product page does not substantiate an independent autonomous-driving capability. Payload arrangement, communications fit and transport accessories remain configuration choices.
The specification table is more useful than inferring values from the visually related Ratel H, but it has a payload ambiguity: the introduction says more than 200 kilograms, while the headline uses a 400-kilogram working-weight label and the loaded/unloaded masses differ by 400 kilograms. This entry does not silently promote that difference into a verified rated payload. The available manufacturer page establishes a marketed product; a named official adoption or unit delivery specific to Ratel M remains a research requirement.
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 ↗ |
| Mobility | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Dimensions | 1,800 × 1,400 × 1,820 mm | Supplier-published configuration; not an independent acceptance result. Source ↗ |
| Mass | 885 kg; 1,285 kg listed with payload | Two published mass conditions; payload label remains ambiguous. 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 | At least 80 km with load | Supplier lists the same value for hard surface and off-road; test conditions unspecified. Source ↗ |
| Speed | 8 km/h | Supplier-published configuration; not an independent acceptance result. Source ↗ |
| Terrain / environment | 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 | Remote ground station; satellite-control option listed | Supplier-published configuration; not an independent acceptance result. 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.