Mercedes-Benz confirms that Apollo robots collected data in a real production environment and that employees taught them production tasks using teleoperation and augmented reality before further autonomy training.
HU-R010 / Deployment watch
Apollo × Mercedes-Benz
Deployment / test evidenceOperator-confirmed factory training
Reliability evidenceNo quantified operating result
Mercedes-Benz confirms Apollo training and data collection in a production environment, but does not publish autonomous task results, operating time or reliability measurements.
Mar 2024agreement announced
Mar 2025operator update
0measured reliability rates
Cite this recordHU-R010 · rev. 6 · Public Data v1.4.0
HumanoidUptime. “Apollo × Mercedes-Benz” (HU-R010), rev. 6, evidence current to 2026-09-04. HumanoidUptime Public Data v1.4.0 (2026). https://humanoiduptime.com/id/HU-R010
- Persistent identity
- HU-R010 · revision 6
- Current record page
- https://humanoiduptime.com/records/apollo-mercedes-berlin/
- Evidence cutoff
- 2026-09-04
- Dataset release
- v1.4.0 · snapshot 2026-09-04
- Immutable dataset
- Versioned JSON
- JSON SHA-256
0e174ef9f5d6de3f140478daa628032f4610761ba3794ec124bd310b33ec9705
What this means
The short version, without reliability jargon
The sources do not say how many robots were used, how long they operated, how many tasks they completed, how much work was autonomous or how often people had to help or recover them.
This is meaningful evidence of real factory integration and a documented path from human teaching toward autonomy. It is not yet evidence that Apollo can perform the work independently or reliably over time.
Evidence verdict
Established. Claimed. Unknown.
EstablishedOperator or independent evidence
- Project and siteApollo training at the Mercedes-Benz Digital Factory Campus in Berlin-Marienfelde[2]
- Intended tasksComponent transport, line delivery and initial component quality checks[2] [1]
- Production-environment dataApollo robots collected data in a production environment for specific MO360 use cases[2]
- Human teaching modeMercedes-Benz employees transferred production knowledge through teleoperation and augmented reality[2]
- Autonomy stageMercedes-Benz says the robots are learning to act autonomously at the campus[2]
ClaimedManufacturer or capability claim
Still unknownNo qualifying public value
- Bounded observation window and operating hours
- Autonomous and teleoperated time shares, supervision and intervention count
- Task attempts, output, success criteria and production throughput
- Exact fleet and hardware versions, downtime, failures and recovery
What the evidence says
Mercedes-Benz confirms that Apollo robots collected data in a real production-development environment at its Berlin-Marienfelde Digital Factory Campus. Employees taught production knowledge through teleoperation and augmented reality, and Mercedes says the robots are learning to act autonomously. A later Apptronik update names Mercedes-Benz within broader mixed teleoperation and autonomous data-collection workflows. None of the reviewed sources publishes operating hours, completed tasks, fleet size, autonomy share, intervention frequency, downtime, failures, recovery time or availability.
01 / Reliability fields
What is known—and missing
Runtime / operating hoursTime accumulated while a robot is operating under the source's stated rules. It may be summed across several robots and does not necessarily include pauses or downtime.Learn more →
Not disclosed: No cumulative operating hours
Availability / uptimeThe share of a defined scheduled period in which a system was able to perform the required function. The time boundary, required function and rules for counting downtime must be stated.Learn more →
Not disclosed: No scheduled-time denominator
Human interventionA human action needed to keep, restore or redirect the robot's work, such as a reset, remote correction or physical assistance.Learn more →
Operator corroborated: Human teaching disclosed; intervention rate unknown
MTBFMean time between failures: the average operating time between one defined failure and the next in a repairable system.Learn more →
Not disclosed: Not disclosed
MTTRAn average time associated with restoring operation after a failure. The acronym is used for repair, restoration or recovery in different contexts, so the included steps must be defined.Learn more →
Not disclosed: Not disclosed
Task outputThe number of reported items moved, parts handled, cycles completed or other units produced.Learn more →
Not disclosed: No task count or success rate
Energy / charging
Not disclosed: No charge/runtime record
Autonomous operationTask execution by the robot without a person continuously issuing the individual control actions. The system may still be supervised and may request help.Learn more →
Operator corroborated: Teleoperation used; autonomy training underway
Fleet sizeThe number of robots included in a reported result or observation.Learn more →
Operator corroborated: Multiple robots described; exact count unknown
Independently measured
Operator corroborated
Manufacturer reported
Capability claim
Not disclosed
Not applicable to this record
02 / Claims and evidence
What each source supports
Project and site
Operator corroborated
Apollo training at the Mercedes-Benz Digital Factory Campus in Berlin-Marienfelde
Mercedes-Benz identifies the robot, operator and production-development site. This establishes a real production environment, not routine autonomous production or reliability performance.
Sources: [2]
Intended tasks
Operator corroborated
Component transport, line delivery and initial component quality checks
Mercedes-Benz and Apptronik describe closely related intralogistics and inspection use cases. Neither source publishes completed-task counts, attempts, throughput, error criteria or production output.
Sources: [2] [1]
Production-environment data
Operator corroborated
Apollo robots collected data in a production environment for specific MO360 use cases
The operator confirms physical data collection in the factory-development environment. It gives no operating-hour total, observation window, robot count, task denominator or indication that the collected time was uninterrupted.
Sources: [2]
Human teaching mode
Operator corroborated
Mercedes-Benz employees transferred production knowledge through TeleoperationA person controls some or all robot actions from a distance rather than the robot selecting those actions by itself.Here, teleoperation describes how Mercedes-Benz employees demonstrated production tasks during training. It is not a published count of interventions during autonomous work.Learn more → and augmented reality
Teleoperation is explicitly part of task teaching. The source does not quantify teleoperated time, supervision, interventions during autonomous execution or how often a person had to recover the robot.
Sources: [2]
Autonomy stage
Operator corroborated
Mercedes-Benz says the robots are learning to act autonomously at the campus
This is evidence of an autonomy-development stage, not proof of unsupervised production work. No autonomous-time share, task-success rate or transition date is disclosed.
Sources: [2]
Later data-collection update
Manufacturer reported
Apptronik names Mercedes-Benz among customer sites using data-collection workflows with teleoperation and autonomous execution
The update describes a broader Apollo 2 data-collection network and does not isolate the Mercedes site, task, robot count, operating time or share of each operating mode. HumanoidUptime does not apply the Apollo 2 configuration retroactively to the earlier Mercedes activity.
Sources: [3]
Commercial framework
Manufacturer reported
Apptronik announced a commercial agreement to explore Apollo manufacturing applications in March 2024
The agreement dates the public program and planned use cases. It does not disclose a purchase quantity, completed deployment, paid production service or reliability result.
Sources: [1]03 / Evidence over time
How the public record changed
This is a history of public knowledge, not proof that robot performance changed on these dates. Earlier states were reconstructed later from dated sources; the reconstruction date remains visible.
A commercial exploration agreement is announced
Apptronik announced an agreement with Mercedes-Benz to identify Apollo applications in manufacturing and described intended logistics and inspection use cases. It did not publish a site-specific operating result, robot count or reliability measurement.
0/9 applicable fields disclosedCoverage at this knowledge date—not performance.
No tracked reliability field had a qualifying public value.
Reconstruction basis and limits
Reconstructed solely from Apptronik's dated March 2024 commercial-agreement announcement.
- Apptronik described its first publicly announced commercial Apollo deployment agreement.
- Potential use cases included delivering kitted parts and inspecting components.
- The announcement discussed intended manufacturing applications rather than measured operation.
- The source did not establish a named factory operating result.
- Commercial agreement language did not fill any tracked reliability field.
Mercedes documents production-environment training
Mercedes-Benz confirmed Apollo robots at its Berlin Digital Factory Campus, production-environment data collection and employee teaching through teleoperation and augmented reality. The source established the operating-mode boundary but still published no runtime or reliability result.
3/9 applicable fields disclosedCoverage at this knowledge date—not performance.
- Human interventionsNot disclosed →Human teaching disclosed; rate unknown
- Task outputIntended tasks only →No result disclosed
- Autonomy modeNot disclosed →Teleoperation used; autonomy training underway
- Fleet sizeNot disclosed →Multiple robots described; exact count unknown
Reconstruction basis and limits
Reconstructed cumulatively from Apptronik's 2024 agreement and Mercedes-Benz's dated 18 March 2025 campus report.
- Mercedes-Benz confirmed multiple Apollo robots at the Berlin-Marienfelde campus.
- Employees transferred production knowledge through teleoperation and augmented reality.
- Mercedes said the robots were learning to act autonomously.
- Training interaction is disclosed, but operational intervention frequency is not.
- No operating hours, task output, downtime, failure or recovery result was published.
Current public evidence state
Mercedes-Benz confirms that Apollo robots collected data in a real production-development environment at its Berlin-Marienfelde Digital Factory Campus. Employees taught production knowledge through teleoperation and augmented reality, and Mercedes says the robots are learning to act autonomously. A later Apptronik update names Mercedes-Benz within broader mixed teleoperation and autonomous data-collection workflows. None of the reviewed sources publishes operating hours, completed tasks, fleet size, autonomy share, intervention frequency, downtime, failures, recovery time or availability.
3/9 applicable fields disclosedCoverage at the latest review—not performance.
- Runtime hoursNot disclosed →No cumulative operating hours
- Availability / uptimeNot disclosed →No scheduled-time denominator
- Human interventionsHuman teaching disclosed; rate unknown →Human teaching disclosed; intervention rate unknown
- Task outputNo result disclosed →No task count or success rate
- Energy / chargingNot disclosed →No charge/runtime record
04 / Deployment timeline
What happened, and when
-
Apptronik announces the Mercedes-Benz agreement
The manufacturer describes planned component delivery, line-side logistics and inspection applications without publishing a fleet commitment or operating result.
[1] -
Mercedes-Benz documents production-environment training
The operator says Apollo robots collected factory data, employees transferred task knowledge through teleoperation and augmented reality, and the robots were learning autonomous action at the Digital Factory Campus.
[2] -
Apptronik describes broader mixed-mode data collection
Apptronik lists Mercedes-Benz among customer and partner sites using related data-collection workflows with teleoperation and autonomous execution, but reports no Mercedes-specific performance result.
[3]
05 / Sources
Trace every finding
-
Source 1Manufacturer statement
Apptronik and Mercedes-Benz enter commercial agreement ↗
Apptronik · Published 2024-03-15 · Accessed 2026-09-04
-
Source 2Operator statement
AI and humanoid robots at the Digital Factory Campus ↗
Mercedes-Benz Group · Published 2025-03-18 · Accessed 2026-09-04
-
Source 3Manufacturer statement
Welcome to Robot Park, where Apptronik's Apollo goes to work ↗
Apptronik · Published 2026-06-30 · Accessed 2026-09-04