Key Takeaways
- Unitree Robotics was founded in 2016 by Wang Xingxing in Hangzhou, China
- The company started with a team of robotics experts from Zhejiang University
- Unitree's first product, Laikago, was released in 2018 weighing 50kg with 3m/s speed
- Unitree Series A funding $15M in 2018 from investors like Matrix Partners
- 2021 Series B raised $50M valuation $500M
- 2024 funding round $100M+ led by Meituan
- Unitree Go2 won Red Dot Design Award 2023
- Partnership with Boston Dynamics for tech exchange 2023
- Deployed in 50+ Chinese factories for inspection by 2024
- Unitree Go1 completed 100m dash in 43 seconds
- B2 pulled 20kg sled at 2m/s speed
- H1 backflip executed 5 times consecutively
- Unitree Go1 robot weighs 12kg and stands 65cm tall
- Go2 model offers 5kg payload capacity with modular batteries
- B2 industrial robot priced at $16,000 with IP67 rating
From a 2016 Zhejiang University team to 10,000 plus shipments, Unitree scaled fast with Go1 and H1.
Related reading
01 · Category
Company History and Founding24 stats
Company History and Founding Interpretation
02 · Category
Financial Data20 stats
Financial Data Interpretation
03 · Category
Market and Recognition22 stats
Market and Recognition Interpretation
More related reading
04 · Category
Performance Metrics22 stats
Performance Metrics Interpretation
05 · Category
Product Portfolio23 stats
Product Portfolio Interpretation
06 · Category
Technical Specifications22 stats
Technical Specifications Interpretation
Cite This Report
This report is designed to be cited. We maintain stable URLs and versioned verification dates. Copy the format appropriate for your publication below.
Priyanka Sharma. (2026, February 24). Unitree Robotics Statistics. Gitnux. https://gitnux.org/unitree-robotics-statistics
Priyanka Sharma. "Unitree Robotics Statistics." Gitnux, 24 Feb 2026, https://gitnux.org/unitree-robotics-statistics.
Priyanka Sharma. 2026. "Unitree Robotics Statistics." Gitnux. https://gitnux.org/unitree-robotics-statistics.
Sources & references
43 datasets cited across this report · attribution is report-level

