Role & capabilities
- Autonomy research
- Modular payload experimentation
- Remote observation
- Primary domain
- Land
- System type
- Ground multirole vehicle
- Developer / manufacturer
- Android Technics
- Origin / production countries
- Russia
- Other names
- Маркер
- Variants / configurations
- Tracked experimental platform; Wheeled experimental platform
- Operators / programme customers
- Developer and partner trials; a military operational fleet is not established by the cited source
Evidence & current status
The live manufacturer page contains predominantly older programme reporting. A current procurement or service-acceptance source remains a gap; media deployment claims have not been promoted to confirmed service.
Marker is a Russian ground robotics programme developed by Android Technics with the Foundation for Advanced Research. The manufacturer's project account dates its start to March 2018 and describes a modular test platform with both tracked and wheeled chassis. Its significance lies in experimentation with navigation, perception, supervisory control and the integration of different equipment packages, rather than one standard production vehicle.
The published performance table distinguishes the two chassis, which differ materially in mass and advertised mobility. These figures are supplier claims for particular platform forms; they should not be combined into a single best-case vehicle. The manufacturer's material includes a report of work at the Vostochny spaceport, providing an application context but not proof of general military acceptance.
Public discussion often moves quickly from research demonstrations to claims of operational capability. This profile keeps Marker in development and trials because the reviewed primary material does not establish a current, named military fleet with documented delivery and acceptance. Claimed autonomy describes functions under development and demonstration, not an assumption of unsupervised operation in every environment.
Sourced specifications
Figures apply to the named configuration. Maximum values are not guaranteed operating performance.
| Specification | Reported value | Context & source |
|---|---|---|
| Configuration | Tracked and wheeled experimental chassis | Supplier-reported; configuration dependent. Source ↗ |
| Mobility | Not established in the reviewed public sources. | Public data gap; no estimate or neighbouring variant value substituted. Source ↗ |
| Dimensions | Not established in the reviewed public sources. | Public data gap; no estimate or neighbouring variant value substituted. Source ↗ |
| Mass | Tracked: 3,000 kg; wheeled: 4,500 kg | Separate platform figures; do not combine. Source ↗ |
| Payload | Not established in the reviewed public sources. | Public data gap; no estimate or neighbouring variant value substituted. Source ↗ |
| Endurance | Not established in the reviewed public sources. | Public data gap; no estimate or neighbouring variant value substituted. Source ↗ |
| Range | Tracked: 600 km; wheeled: 1,000 km | Advertised travel range for separate configurations. Source ↗ |
| Speed | Tracked: up to 70 km/h; wheeled: up to 80 km/h | Supplier maximum-speed claims, not validated fleet performance. Source ↗ |
| Terrain / environment | Not established in the reviewed public sources. | Public data gap; no estimate or neighbouring variant value substituted. Source ↗ |
| Sensors | Not established in the reviewed public sources. | Public data gap; no estimate or neighbouring variant value substituted. Source ↗ |
| Communications / control | Remote control and experimental autonomous functions | Function-level claims; operational acceptance not established. Source ↗ |
| Launch / deployment | Not established in the reviewed public sources. | Public data gap; no estimate or neighbouring variant value substituted. Source ↗ |
Publication history
- — Added sourced land and maritime coverage with domain-specific evidence and limitations.
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.