Monthly evidence digest
Humanoid Robot Market Snapshot — June 2024
7 dated items in our coverage for June 2024.
Computed from dated records in our ledgers; counts reflect our coverage, not the whole market.
Built (UTC) · Latest record date: 2024-06-20
Headline numbers
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.
- Price-history entry
Tokyo Robotics Torobo2: $114,771 starting →
official price record · One-unit introductory price for orders through 2024; regular one-unit list price was JPY 22,500,000. Converted at JPY 156.834282 per USD on 10 June 2024.
Qualifies: Official price-history record
Robot announcements (4)
Robot announced date. Year-only and unknown dates are excluded.
- Announcement
Stanford HumanPlus announced →
Announcement date recorded for Stanford HumanPlus.
- Announcement
Tokyo Robotics Torobo2 announced →
Announcement date recorded for Tokyo Robotics Torobo2.
Sources (8)
- Announcement
Galbot G1 announced →
Announcement date recorded for Galbot G1.
Sources (12)
- Galbot G1 product page (specifications) ↗
- Galbot G1 cumulative 2025 shipments exceed 1,200 units (Gelonghui) ↗
- abc Co. receives Galbot G1 unit for domestic verification (press release) ↗
- Galbot's humanoid robots do the boring stuff, and that's the point (KrASIA) ↗
- Galbot unveils G1 at BAAI Conference 2024 ↗
- Galbot G1 JD flagship-store market price and order report ↗
- Foreign Exchange Rates H.10, week ending 27 February 2026 ↗
- Galbot developer platform and SDK ↗
- Galbot contact page (whole-machine purchase inquiry form) ↗
- GALBOT G1 listing on JD.com (linked from the Galbot G1 page) ↗
- Galbot G1: Our First Embodied AI Product Embodying the Future of Industrial and Home Autopilot ↗
- Galbot company introduction: native brand and G1/S1 model names ↗
- Announcement
KIT ARMAR-7 announced →
Announcement date recorded for KIT ARMAR-7.
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.
- Price-history entry
Tokyo Robotics Torobo2: $114,771 starting →
official price record · One-unit introductory price for orders through 2024; regular one-unit list price was JPY 22,500,000. Converted at JPY 156.834282 per USD on 10 June 2024.
New deployment records (1)
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.
| Stage | E0 | E1 | E2 | E3 | E4 | E5 | Total |
|---|---|---|---|---|---|---|---|
| Announced | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| Pilot | 0 | 0 | 1 | 0 | 0 | 0 | 1 |
| Commercial | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| Production | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| Ended | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
- Earliest month-dated source disclosure; start unknown
Apptronik Apollo · GXO Logistics →
pilot · E2 · unknown units basis. GXO and Apptronik said in June 2024 that they were conducting a joint proof of concept and evaluating Apollo in a laboratory. Deployment at an unnamed U.S. distribution center was a later step contingent on readiness; the release gives no exact start date, robot count or paid terms.
Timeline claims stated (0)
Claim statedAt date, never its future target date.
No month-dated records in our coverage.
Timeline claims resolved (0)
Claim resolvedAt date with a recorded non-pending outcome. Statements and resolutions are separate dated items.
No month-dated records in our coverage.
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 (0)
Each policy timeline entry's date; future effective dates do not enter a month-to-date report.
No month-dated records in our coverage.
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.
- Model release / introduction
OpenVLA →
OpenVLA adapts a Prismatic vision-language backbone to tokenized robot actions; its authors describe the policy as 7B. The code and checkpoint card specify MIT, while the repository explicitly states that pretrained models also inherit the Llama 2 Community License Agreement.
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 (0)
Each capability item's date, with evidence type and source-stated autonomy retained.
No month-dated records in our coverage.
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.