humanoidversus
Find a robot

Monthly evidence digest

Humanoid Robot Market Snapshot — April 2026

35 dated items in our coverage for April 2026.

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

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

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

Headline numbers

Robot announcements
10
Documented catalog additions
0
Price-history records
0
New deployment records
1
Timeline claims stated
10
Timeline claims resolved
5
Market figures published
4
Policy timeline events
0
Security advisories disclosed
0
Models released / introduced
3
Datasets released
0
Competition result files
1
News articles published
0
Task evidence records
1
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

    1X NEO: production start met →

    The manufacturer explicitly reported that Hayward production had commenced. The update did not give the production-start date or confirm consumer deliveries.

    Qualifies: Timeline outcome: met

    Sources (1)
  2. Claim resolved

    Figure 03: volume met →

    Figure's production update stated that the hourly cycle time had been demonstrated; no annualized output is inferred.

    Qualifies: Timeline outcome: met

    Sources (1)
  3. Claim resolved

    Figure 03: production start met →

    The manufacturer explicitly reported production-phase operation. It did not supply the start date or establish consumer deliveries.

    Qualifies: Timeline outcome: met

    Sources (1)

Robot announcements (10)

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 (0)

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

No month-dated records in our coverage.

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.

Deployment records by stage and evidence grade at build time
StageE0E1E2E3E4E5Total
Announced0000000
Pilot0100001
Commercial0000000
Production0000000
Ended0000000

Timeline claims stated (10)

Claim statedAt date, never its future target date.

Timeline claims resolved (5)

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

Market figures published (4)

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

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 (3)

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 (1)

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

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 (1)

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 →