How we count

A claim should never look like a fact. Every number on this site links to its source, and every badge says who vouches for it.

Evidence badges

A badge covers everything an observation states, robot counts included: if only the maker gives a count, that count stays a company claim even when the customer has confirmed the project.

"At work"

A customer site counts as at work when all of these hold:

• The customer or operator confirmed it, or someone independent saw it.
• That evidence is less than 12 months old. Older sites are shown as "unverified since" a date.
• The robots were working, as a pilot or in production. An announced project does not count until it starts.
• It has not ended.

A maker using its own robots in its own plants counts only when someone independent saw it. Pilots count, and the split between production and pilots is shown.

The site counts robots, not sites. A counted site that does not disclose how many robots it uses adds at least one, so the total is a lower bound ("4+"); it also covers only sites this tracker has documented. Sites where only the maker says robots are working are named next to the number, never added to it.

Shipped versus at work

The home page shows an analyst's estimate of robots shipped next to the robots proven at work. They measure different things, so they are shown side by side, never as a ratio. Analysts also define the market differently (Omdia counts general-purpose embodied robots, Counterpoint counts humanoid robots), so each chart uses one analyst's figures only.

Promises and deadlines

• The deadline is the latest date the words allow. "By 2027" ends on 31 December 2027; "February or March" ends on 31 March. The original wording is shown next to it. Promises with no time frame get no countdown.
• "Past deadline" means the deadline has passed and no delivery is on record. It is not a verdict: we mark a promise missed only when a source shows it did not happen.
• "Deadline moved" means a later promise replaced it. Each promise keeps its own deadline, so the history stays visible.
• "Delivered N days late" is counted from when it was delivered, never from when the result was reported. When the delivery date is unknown, the site says only "Delivered".
• Day counts use your own calendar date and update in your browser.
• A promise is dated when it was made. When only a report of it exists, it is dated by the report's publication, and the promise names the report.

Robots built, shipped and promised

• Makers' own counts (home Fig. 01). Analysts publish per-company figures only every half year, so this chart uses what each maker reports itself: production milestones, filings and announcements. Makers count different things (built, shipped or sold; all robot forms or humanoids only), so each maker gets its own line, never a stack. A line steps up when the maker reports and stays flat until the next report: flat means "last reported", not "none made".
• Analyst estimates (Fig. 07 and 08) stay separate from makers' counts, one analyst per chart.
• Robots promised (Fig. 02). A promise that names a number of robots is compared only with a count of the same thing over the same window: robots built never fill a promise about robots delivered. There is no pace verdict, because factories ramp up unevenly and an unreported count is not zero.

Stock prices

• Only companies that make humanoid robots and are listed themselves. Owners and affiliates (Hyundai for Boston Dynamics, Swancor for AgiBot) are left out, because their prices mostly reflect other businesses.
• Daily closing prices of completed trading days, in the company's own currency, adjusted for stock splits but not for dividends. A company listed in two places is charted on its primary listing.
• Robot milestones are marked by date: a line for a known day, a shaded band when only the month is known. Markers show dates only. They do not show that a release moved the price; for most of these companies robots are a small part of the business.
• Stock charts appear only with a licensed price provider. Until one is in place, this site shows none.

Sources

• We prefer primary sources: company and customer announcements, regulatory filings and earnings-call transcripts.
• Other trackers (Axis Intelligence, the Humanoid Reality Index, humanoidversus.com, twoweeks.lol) helped us find leads; we cite the original sources.
• Analyst figures are quoted individually with attribution; we do not republish reports.
• Source titles are quoted as their publishers wrote them, typos included (marked [sic]).
• Photos are used only under a license that allows it (public domain or Creative Commons), credited next to the photo. Where there is none, a robot card shows a still from an official video on the maker's own YouTube channel, which plays in YouTube's player; otherwise a plain outline labeled "Illustration".

Latest videos and news

An automatic feed of new videos from official company YouTube channels and headlines from robotics news sites. It is not checked by us and is kept apart from the data above; nothing in it feeds a chart. A feed is shown only once its terms allow it.

Calendar

• Industry events (conferences, trade fairs, robot competitions) and company dates (results, shareholder meetings, launch events, listings). Promise deadlines and past robot reveals are not calendar events.
• A date counts as announced only when the organizer or company has published it, and each event links that source. Until then the event is listed at its expected month, with the reason, and cannot be added to a calendar yet.
• Times are the organizer's local time; the page also shows your own. Subscribed calendars get new and changed dates by themselves; a cancelled event leaves them.

Privacy

Visits are counted with Cloudflare Web Analytics, which sets no cookies and does not follow you across other sites. The site has no accounts and no forms.