Quick answer
Figure's April 29, 2026 BotQ update reports over 350 Figure 03 robots built and a demonstrated one-robot-per-hour cycle, up from one per day in under 120 days. This is a manufacturing milestone; it does not mean that every robot went to a paying customer.
The numbers in plain English
There are three different measures to keep separate: cumulative robots built, a demonstrated production cycle and completed customer shipments. The announcement supports the first two. It does not provide a customer shipment breakdown or a guaranteed annual output.
Our interpretation is that a faster demonstrated cycle makes fleet growth more plausible, but it does not remove the constraints of utilization, component supply, yield, staffing or maintenance. Multiplying an hourly cycle by every hour in a year produces a theoretical scenario rather than a forecast. We do not assume a 24-hour schedule or choose an arbitrary utilization percentage to turn that scenario into an annual shipment claim.
This distinction matters when comparing factories. A manufacturer may report assembly capacity while another reports deliveries, orders or units operating at customer sites. Those measures cannot be ranked as though they were interchangeable. A buyer should ask for the measurement period, product generation and destination of units before comparing totals.
Where the fleet goes
Figure describes allocations to internal research, data collection, housework efforts and commercial use-case development. It does not publish the proportion for each destination. These categories are useful context for the build count, but do not establish how many customers have received a robot or how many robots perform paid work.
For procurement, request the evidence relevant to your intended task: deployment scope, acceptance testing, uptime, intervention rate, service coverage and recovery procedures. Fleet growth may support development, while a particular workflow can still require substantial integration and evaluation. A build count alone does not answer those operational questions.
What Helix and S0 add
The same update describes Helix's System 0 (S0) as a whole-body controller and discusses adding perception of the surrounding environment. S0 should not be described merely as a perception subsystem that another controller consumes. The update connects growing fleet experience with software development; it does not certify identical capability or software versions on every shipped unit.
Our interpretation is that manufacturing and software progress can reinforce each other: a larger operated fleet creates more opportunities to observe failures and evaluate updates. That is a development argument, not proof that every manufactured unit has the latest demonstrated behavior. Buyers should confirm the supported software release and acceptance criteria for the units actually offered to them.
How it stacks up
Use the production tracker for dated manufacturer evidence and unknowns. Three comparison sources answer different questions:
- Boston Dynamics' January 5 announcement describes Atlas production starting in 2026 and a committed deployment schedule for Hyundai and Google DeepMind. Scheduled shipments are not confirmation of delivery.
- Tesla's January 28 update, page 8, discusses an Optimus line under construction and production planned before year-end. Eventual line capacity is not actual output.
- Unitree's G1 manufacturer page identifies the platform, but does not establish a comparable production count in the reviewed page.
These sources do not support a claim that the rest of the industry ships only dozens or low hundreds of robots, or that Figure has the industry's largest or fastest ramp. A source-backed comparison can remain useful while leaving a ranking unresolved. The information manufacturers choose to disclose differs, and a missing number should remain unknown.
Where to go next
- Review the Figure 03 profile and Figure manufacturer page.
- Use the comparison tool for platform differences and warehousing and logistics applications for task requirements.
- Read the economics guide to distinguish a quote, a capacity claim and a cost-of-ownership scenario.
FAQ
How many Figure 03 robots were built?
Figure reported over 350 in its April 29 update. That count includes internal uses and is not a disclosed customer shipment total.
Is one robot per hour a delivery promise?
No. It is the demonstrated BotQ cycle reported in that announcement, not an annual output or delivery guarantee.
What is S0?
Figure describes System 0 as Helix's whole-body control model and reports progress in perception-conditioned control.
What should a buyer verify?
Confirm the actual commercial offer, software version, supported task, acceptance criteria and service agreement through the manufacturer. See the Figure profile.
Sources and review
Sources checked 2026-10-01 UTC (September 30 in California). Figure's production figures remain dated April 29, rather than presented as new October measurements.
- Figure production update, April 29, 2026: build count, demonstrated cycle, fleet allocation categories and S0 description.
- Boston Dynamics Atlas announcement, January 5, 2026: planned production and scheduled deployments.
- Tesla Q4/FY2025 update, January 28, 2026, page 8: line construction and production plan.
- Unitree G1 product page, undated: platform identity, without a comparable output total.
