Quick answer
Beijing's published result names Team Monkey King's Shandian (Lightning) as the winner on April 19, 2026, with a 50:26 time. The event report records over 100 teams, rather than an audited total of individual robots or manufacturers. This article separates that race result from manufacturer specifications and commercial readiness.
The result and the timing rules
The Beijing city result report describes a 21.0975-kilometer course. Autonomous and remotely controlled entrants shared a ranking, but remote-control times received a 1.2 weighting factor. A raw crossing time and a ranked result therefore answer different questions. Comparisons should specify which time they use.
The Beijing Economic-Technological Development Area report attributes the winning team to HONOR and explicitly identifies 50:26 as net time. HONOR's manufacturer event page presents its D1 and A1 robotics platforms and a half-marathon achievement; the event result supplies the timed outcome. We do not use the manufacturer landing page as evidence for every race number.
The result is a significant speed headline. Describing 50:26 as recreational human half-marathon pace would be misleading. However, a robot competition is not a human athletics record: assistance, timing adjustments, equipment and competition rules need to be considered before comparing performances.
Which robots participated?
| Evidence | What is established | What remains unknown here |
|---|---|---|
| Beijing published results | Lightning, Team Monkey King, winning result | Complete verified participant-to-model inventory |
| Beijing event reporting | Over 100 competing teams | Audited individual robot and manufacturer totals |
| HONOR manufacturer page | D1 and A1 platform identities | Race-unit-specific weight, degrees of freedom and battery configuration |
A team count is not a robot count. The earlier 300+ robots and 26+ manufacturers figures are not retained as verified facts without a precise supporting source and a definition of what was counted. No complete participant list or specification table is reconstructed from photographs or brand names.
Catalog platforms must also be distinguished from competition configurations. A race entry bearing a manufacturer's name does not establish that it used the manufacturer's retail model, standard battery or published software version. We will link specific race robots to catalog profiles when that identity is supported by manufacturer evidence.
What the race means for buyers
The following is procurement analysis, rather than measured outcomes from the event.
Ask about repeatability. A timed finish is useful evidence for a particular run. A buyer should ask how often the robot completes the required route, under which surfaces and environmental conditions, and with how much supervision. A fast demonstration alone does not supply a service-level commitment.
Ask about interventions. The city report describes battery swaps and penalties being recorded. A finishing time does not establish zero falls, uninterrupted operation, thermal margin or an entire work shift on one charge. Buyers should request logs that distinguish autonomous operation, recovery, battery changes and human assistance.
Match the task. Running a course and handling irregular items are different capabilities. For a warehouse deployment, the useful question is whether a platform can complete the actual handling workflow safely and repeatedly. Speed can matter, but payload handling, manipulation, integration and service support also belong in the evaluation.
Separate public participation from supply. Entering a race does not prove customer shipments, production capacity or a purchase channel. The event is a starting point for investigating manufacturers; it cannot substitute for availability evidence. The race also provides no basis for asserting that locomotion costs are falling every quarter or that most failures occurred in a particular five-kilometer section.
Where to go next
- Browse the robot catalog and manufacturer directory for separately sourced platform records.
- Use robot comparisons to compare catalog specifications without assuming a race configuration.
- Read warehousing and logistics applications to connect mobility to a specific procurement task.
FAQ
Who won the Beijing robot half-marathon?
The published Beijing result names Lightning from Team Monkey King, associated with HONOR, with a 50:26 result.
How many robots competed?
The reviewed event report establishes over 100 teams. Individual robot and manufacturer totals are not verified in this article.
Does the finish prove uninterrupted battery operation?
No. The result alone does not establish intervention history, battery endurance or fault-free operation.
Does winning establish commercial readiness?
No. Request task-specific reliability, safety, service and availability evidence before a procurement decision.
Sources and review
Sources checked 2026-10-01 UTC (September 30 in California). Publication dates remain distinct from this review date.
- Beijing city results and timing methodology, April 19, 2026: winner, time, course, team count and weighting rules.
- Beijing Economic-Technological Development Area event report, April 21, 2026: HONOR team attribution and net-time terminology.
- HONOR robotics event page, undated live manufacturer page: platform identity only; no invented race specifications.
