humanoidversus
Find a robot

Monthly evidence digest

Humanoid Robot Market Snapshot — June 2026

22 dated items in our coverage for June 2026.

Computed from dated records in our ledgers; counts reflect our coverage, not the whole market.

Built (UTC) · Latest record date: 2026-06-30

Method and counting rules ↓Monthly Atom feed →Data changelog →

Headline numbers

Robot announcements
9
Documented catalog additions
0
Price-history records
1
New deployment records
3
Timeline claims stated
1
Timeline claims resolved
1
Market figures published
0
Policy timeline events
1
Security advisories disclosed
0
Models released / introduced
1
Datasets released
0
Competition result files
0
News articles published
0
Task evidence records
5
Calendar events started
0

Notable by recorded evidence

The latest 10 matching items: deployments at E3 or higher in pilot, commercial or production stages (excluding order/capacity rows); official price-history records; and timeline resolutions marked met or slipped. Sorted by record date, then stable record ID. No editorial scoring.

  1. Claim resolved

    Figure 03: other met →

    Figure explicitly reported the arrival and demonstration. This is a customer-site milestone, not a general-availability announcement or confirmation of the first external delivery.

    Qualifies: Timeline outcome: met

    Sources (1)
  2. Price-history entry

    Unitree R1: $4,900 starting →

    official price record · Manufacturer's 24 June 2026 ready-stock announcement; $4,900 is the AIR/family starting price, not standard R1.

    Qualifies: Official price-history record

    Sources (1)

Robot announcements (9)

Robot announced date. Year-only and unknown dates are excluded.

Documented catalog additions (0)

News publication date for an explicit robot record creation (field record, from null). One earliest addition per robot; specification additions do not qualify.

No month-dated records in our coverage.

Price-history records (1)

Each dated priceHistory entry, including initial prices, targets and subscriptions. An entry does not necessarily establish an amount change.

New deployment records (3)

Start date; if absent, the earliest month-dated source publication as a disclosure date. Counts are records, not deployed units. Stage and evidence describe the current ledger at this build.

Deployment records by stage and evidence grade at build time
StageE0E1E2E3E4E5Total
Announced0000000
Pilot0210003
Commercial0000000
Production0000000
Ended0000000
  • Earliest month-dated source disclosure; start unknown

    Apptronik Apollo 2 · GXO Logistics →

    pilot · E1 · unknown units basis. Apptronik said in June 2026 that Apollo 2 data-collection workflows were active at GXO customer sites, using teleoperation and autonomous execution to train Gemini Robotics models. This training pilot uses Apollo 2, available in wheeled and bipedal configurations; the site's configuration, location, start date and robot count are not disclosed.

    Sources (1)
  • Earliest month-dated source disclosure; start unknown

    Apptronik Apollo 2 · Mercedes-Benz →

    pilot · E1 · unknown units basis. Apptronik said in June 2026 that Apollo 2 data-collection workflows were active at Mercedes-Benz customer sites, using teleoperation and autonomous execution to train Gemini Robotics models. This training pilot uses Apollo 2, available in wheeled and bipedal configurations; the site's configuration, location, start date and robot count are not disclosed.

    Sources (1)
  • Earliest month-dated source disclosure; start unknown

    Figure 03 · BMW Group →

    pilot · E2 · unknown units basis. BMW announced a Figure 03 sequencing project in Spartanburg's Hall 52 in June 2026, and Figure published its first demonstration of that logistics workflow shortly afterward. This supports a pilot, with no disclosed fleet size, exact deployment start date or explicit site-level autonomy mode.

    Sources (2)

Timeline claims stated (1)

Claim statedAt date, never its future target date.

Timeline claims resolved (1)

Claim resolvedAt date with a recorded non-pending outcome. Statements and resolutions are separate dated items.

  • Claim resolved

    Figure 03: other met →

    Figure explicitly reported the arrival and demonstration. This is a customer-site milestone, not a general-availability announcement or confirmation of the first external delivery.

    Sources (1)

Market figures published (0)

PublishedAt date for estimates, forecasts, company reports, capacity and funding, retaining each kind and metric. Figures are never summed.

No month-dated records in our coverage.

Policy timeline events (1)

Each policy timeline entry's date; future effective dates do not enter a month-to-date report.

Security advisories disclosed (0)

DisclosedAt date, not vendor response or verification dates.

No month-dated records in our coverage.

Models released / introduced (1)

Model released date; this can be an announcement or paper introduction, not necessarily public weights.

Datasets released (0)

Dataset released date, retaining its publisher's release scope.

No month-dated records in our coverage.

Competition result files (0)

Result date for competition benchmarks only. One edition/run file, not one count per competitor; event dates may precede result publication.

No month-dated records in our coverage.

News articles published (0)

PublishedAt's own calendar date, not the updatedAt or verification date. One count per article.

No month-dated records in our coverage.

Task evidence records (5)

Each capability item's date, with evidence type and source-stated autonomy retained.

Calendar events started (0)

Event ledger start date. Future events are excluded until that date; these are calendar records, not a new-event announcement count.

No month-dated records in our coverage.

Method and coverage limits

Computed from dated records in our ledgers; counts reflect our coverage, not the whole market. Month buckets use the record’s own date string, including an article’s written timezone date. We never convert it to another timezone. Month-precision dates are retained; year-only and unknown dates cannot be assigned to a month. Exact dates after the build date are excluded, including future dates within the current month.

Verification dates are not announcements, releases or record-creation dates and do not enter these totals. The catalog has no addedAt field: only explicit robot record creations documented in news count as additions. A robot can appear in both announcements and additions; totals count dated ledger items, not unique robots or independent market events.

Deployments without a start date use the earliest source publication with month precision as a disclosure date, visibly labelled on the item. Undated deployments are excluded. Evidence grades and stages describe the current ledger, so a later verification or reclassification may change a past report’s breakdown.

These pages are generated from current records at each build, including past months. They are not frozen quarterly vintages or a census. Linked records retain qualifications, source attribution and unknowns. A missing item does not establish that nothing happened in the market.

Detail pages are generated for months with at least five dated items, plus the current month to date. Sparse past months are summarised by year on the archive. A current month with fewer than five items is noindex; only generated indexable months appear in the sitemap and Atom feed. Sitemap lastmod uses the latest dated item in that month, preserving month precision when no exact day is known. The Atom feed’s updated date is the UTC build date because every digest is regenerated.

Verification methodology → · Send a sourced correction →