Deployment

Humanoid Robot Deployment Timeline

Events are ordered by announcement date with the customer and task retained. Unknown unit counts are not estimated.

Source observations through 2026-07-31. Analysis revised separately.Open all humanoid data charts

Data summary

What is included

Events are ordered by announcement date with the customer and task retained. Unknown unit counts are not estimated.

Visible rows

11

Dataset scope

TechniaHQRobot source-linked dataset

Interactive infographic

Humanoid Robot Deployment Timeline

Events are ordered by announcement date with the customer and task retained. Unknown unit counts are not estimated.

  1. Apptronik Apollo

    Announcement
    2024-03-15
    Client
    Mercedes-Benz
    Site
    Mercedes-Benz manufacturing operations
    Task
    Parts delivery, kitting and inspection pilot
    Status
    Pilot announced

    The announcement does not disclose unit count or a production deployment date.

    Read source ↗
  2. Agility Digit

    Announcement
    2024-06-05
    Client
    GXO Logistics
    Site
    Flowery Branch, Georgia, United States
    Task
    Moving totes between an AMR and conveyor
    Status
    Commercial deployment

    The initial deployment date is documented; robot unit count is not disclosed in the cited update.

    Read source ↗
  3. Agility Digit

    Announcement
    2024-11-13
    Client
    Schaeffler Group
    Site
    Not recorded
    Task
    Manufacturing use cases
    Status
    Strategic investment and deployment agreement

    Unit count and site schedule not disclosed.

    Read source ↗
  4. Apptronik Apollo

    Announcement
    2025-02-25
    Client
    Jabil
    Site
    Jabil manufacturing operations
    Task
    Robot manufacturing and selected factory operations
    Status
    Pilot and strategic collaboration

    Unit count not disclosed.

    Read source ↗
  5. Figure 02

    Announcement
    2025-11-19
    Client
    BMW Manufacturing
    Site
    Spartanburg, South Carolina, United States
    Task
    Sheet-metal loading in BMW X3 production
    Status
    Completed 11-month production deployment reported by Figure

    The source states more than 90,000 parts loaded, more than 1,250 runtime hours and contribution to more than 30,000 BMW X3 vehicles; robot unit count is not disclosed.

    Read source ↗
  6. Agility Digit

    Announcement
    2025-11-20
    Client
    GXO Logistics
    Site
    Flowery Branch, Georgia, United States
    Task
    Tote handling
    Status
    Operational milestone

    Task count is not a robot unit count and is excluded from cumulative deployed-unit totals.

    Read source ↗
  7. Agility Digit

    Announcement
    2025-12-10
    Client
    Mercado Libre
    Site
    Not recorded
    Task
    Distribution and logistics operations
    Status
    Commercial agreement

    Unit count and deployment schedule not disclosed.

    Read source ↗
  8. Agility Digit

    Announcement
    2026-02-19
    Client
    Toyota Motor Manufacturing Canada
    Site
    Toyota facilities in Canada
    Task
    Manufacturing and logistics work following a pilot
    Status
    Commercial agreement following pilot

    Deployment schedule and unit count were not disclosed.

    Read source ↗
  9. Figure 03

    Announcement
    2026-05-26
    Client
    Catalyst Brands
    Site
    Reno distribution center, Nevada, United States
    Task
    Supply-chain and distribution work
    Status
    Commercial agreement

    Deployment schedule and unit count were not disclosed.

    Read source ↗
  10. AgiBot A2 Ultra

    Announcement
    2026-06-29
    Client
    Longcheer Technology
    Site
    Consumer-electronics factory
    Task
    Multi-workflow factory operation including inspection and material handling
    Status
    Documented factory operation

    The official report describes more than 64 hours and 64,828 tasks; it does not disclose deployed robot count.

    Read source ↗
  11. Figure 03

    Announcement
    2026-06-30
    Client
    BMW Manufacturing
    Site
    Hall 52, Spartanburg, South Carolina, United States
    Task
    Sequencing use case
    Status
    Deployment update

    The official update confirms arrival at Hall 52 but does not disclose robot count.

    Read source ↗

Accessible data table

The table contains the same source-linked records used by the chart. It is the reference when labels overlap or a visual scale compresses values.

Source-linked data used in the infographic
RobotAnnouncementPilotDeploymentClientSiteTaskConfirmed unitsEvidenceSource
Figure 022025-11-19Not publicly disclosedNot publicly disclosedBMW ManufacturingSpartanburg, South Carolina, United StatesSheet-metal loading in BMW X3 productionNot publicly disclosedCustomer confirmedFigure official BMW production reportChecked 2026-07-31
Figure 032026-06-30Not publicly disclosed2026-06-30BMW ManufacturingHall 52, Spartanburg, South Carolina, United StatesSequencing use caseNot publicly disclosedCustomer confirmedFigure official F.03 BMW deployment updateChecked 2026-07-31
Figure 032026-05-26Not publicly disclosedNot publicly disclosedCatalyst BrandsReno distribution center, Nevada, United StatesSupply-chain and distribution workNot publicly disclosedOfficial announcementFigure official Catalyst Brands agreementChecked 2026-07-31
Agility Digit2024-06-052024-06-052024-06-05GXO LogisticsFlowery Branch, Georgia, United StatesMoving totes between an AMR and conveyorNot publicly disclosedCustomer confirmedAgility Robotics official Digit GXO deployment updateChecked 2026-07-31
Agility Digit2025-11-20Not publicly disclosedNot publicly disclosedGXO LogisticsFlowery Branch, Georgia, United StatesTote handlingNot publicly disclosedCustomer confirmedAgility Robotics official 100,000-tote milestoneChecked 2026-07-31
Agility Digit2026-02-19Not publicly disclosedNot publicly disclosedToyota Motor Manufacturing CanadaToyota facilities in CanadaManufacturing and logistics work following a pilotNot publicly disclosedCustomer confirmedAgility Robotics official Toyota agreementChecked 2026-07-31
Apptronik Apollo2024-03-152024-03-15Not publicly disclosedMercedes-BenzMercedes-Benz manufacturing operationsParts delivery, kitting and inspection pilotNot publicly disclosedCustomer confirmedApptronik official Mercedes-Benz agreementChecked 2026-07-31
AgiBot A2 Ultra2026-06-292026-06-23Not publicly disclosedLongcheer TechnologyConsumer-electronics factoryMulti-workflow factory operation including inspection and material handlingNot publicly disclosedCustomer confirmedAgiBot official Longcheer factory-operation reportChecked 2026-07-31
Agility Digit2024-11-13Not publicly disclosedNot publicly disclosedSchaeffler GroupNot publicly disclosedManufacturing use casesNot publicly disclosedCustomer confirmedAgility Robotics official Schaeffler agreementChecked 2026-07-31
Agility Digit2025-12-10Not publicly disclosedNot publicly disclosedMercado LibreNot publicly disclosedDistribution and logistics operationsNot publicly disclosedCustomer confirmedAgility Robotics official Mercado Libre agreementChecked 2026-07-31
Apptronik Apollo2025-02-252025-02-25Not publicly disclosedJabilJabil manufacturing operationsRobot manufacturing and selected factory operationsNot publicly disclosedCustomer confirmedApptronik official Jabil collaborationChecked 2026-07-31

Methodology

How the dataset is built

Timeline events use the date explicitly published by the company or customer. Task volumes and runtime are stored separately from robot unit counts. Rows with undisclosed unit counts appear on the timeline but contribute nothing to cumulative deployment-unit charts.

Editorial analysis

Eleven events include different milestones

The timeline contains agreements, pilots, operational updates and deployment announcements. Figure’s BMW records and Digit’s GXO records include more than one milestone. Repeated appearances do not necessarily identify additional fleets.

Announcement and operation dates can differ

A publication date tells readers when an event was reported. A pilot date or deployment date describes another point in the project. Where the source does not identify the operational date, the timeline retains that gap instead of converting the announcement into a confirmed start.

Avoid counting the same project twice

Before adding unit totals, resolve whether an update concerns robots already counted in an earlier event. The current records do not provide sufficient confirmed quantities for a cumulative installed-base chart. Customer, site and task are more useful identifiers here.

Frequently asked questions

Can the timeline show the total number of deployed robots?

No. Confirmed unit counts are missing for these events, and multiple announcements can refer to the same project.

Sources

Related humanoid infographics

Continue with the source-linked humanoid catalog

Open individual robot records for manufacturer, origin, dimensions, availability, public price status and official product links.