Role & capabilities
- Ground reconnaissance
- Modular mission equipment
- Primary domain
- Land
- System type
- Ground multirole vehicle
- Developer / manufacturer
- Israel Aerospace Industries — ELTA
- Origin / production countries
- Israel
- Other names
- No additional names recorded
- Variants / configurations
- Not distinguished in reviewed sources
- Operators / programme customers
- Not identified in reviewed sources
Evidence & current status
Reviewed 21 September 2026; named product documented, current fleet quantity not independently established.
RoBattle is an IAI ELTA robotic vehicle offering for reconnaissance and modular support roles. Its current designation is ELA-6681. IAI introduced the system at Eurosatory in June 2016 and continues to list it in the company's ground-robotics portfolio. The introduction describes a modular robotics kit covering vehicle control, navigation, mapping, sensors and mission equipment.
The original announcement allows both wheeled and tracked configurations and several degrees of autonomy. Those choices matter: a single photograph or demonstration vehicle cannot establish a universal mass, payload or mobility specification for the family. The advertised mission packages include observation sensors, manipulators and remotely controlled equipment.
The current page establishes continued marketing, while the reviewed manufacturer material does not identify a specific new delivery batch or customer acceptance. RoBattle therefore remains supplier-reported in this catalogue. Its autonomous mobility functions should be distinguished from the control and approval of any mounted mission equipment. It also remains separate from REX, RobARC and RobDozer, which have their own product designations and different principal support roles.
Sourced specifications
Figures apply to the named configuration. Maximum values are not guaranteed operating performance.
| Specification | Reported value | Context & source |
|---|---|---|
| Configuration | Modular robotic reconnaissance and support platform | Supplier-published configuration; not an independent acceptance result. Source |
| Mobility | 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 |
| 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 | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source |
| Speed | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. 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 and autonomous functions described; configuration-specific | 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
- — Published reference update.
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.