Отчет о развитии городской робототехники 2026: рынок, продукты, цепочка поставок и перспективы
City Robotics Industry Development Report 2026: Market, Products, Supply Chain and Outlook
Executive Summary
This report asks: How is the global city-robotics market developing through 2026, and what do urban labor constraints, modular autonomous-mobile-space products, RaaS positioning and reported manufacturing capabilities mean for platform-vendor screening and city-robotics pilot procurement?
The available evidence supports market scanning rather than a deployment or investment conclusion. Reported global city-robotics market value was USD 4.2 billion in 2025, with a reported 28.6% compound annual growth rate for 2026–2035. These figures indicate a market narrative of rapid expansion, but they are single-source context with no disclosed market boundary or forecast methodology available in this evidence package.
For European mobility buyers, 105,000 bus-driver vacancies in 2023 provide a measurable labor-constraint signal. The figure does not prove that autonomous shuttles will resolve staffing shortages. It does, however, justify a structured pilot screen where a city has defined short-distance routes, a recurring service gap, and a validated operating pathway.
The product evidence points to an autonomous-mobile-space proposition rather than a single fixed vehicle category. Reported offerings span RoboBus, RoboTaxi, RoboShop and RoboVan, built around a claimed modular robotic-chassis architecture. This structure potentially allows buyers to assess one platform across mobility, retail and service-space cases, but it also shifts procurement from a vehicle comparison toward a combined platform, configuration, service and operating-responsibility assessment.
Manufacturer information should be treated as supplier-discovery evidence, not delivery assurance. Reported validation centers, additive-manufacturing positioning and stated annual capacity of 2,000 vehicles establish questions for factory qualification. They do not demonstrate actual output, utilization, lead time, quality-system performance, product availability, public-road authorization or readiness for a fleet commitment. The recommended next step is an evidence-gated pilot RFQ rather than a capacity-led award.
Scope, Definitions and Evidence Limitations
The scope is global city robotics and autonomous mobile-space platforms, with particular relevance to Europe for urban labor constraints. It covers RoboBus, RoboTaxi, RoboShop, RoboVan and modular robotic-chassis-based mobile spaces; autonomous shuttle and short-distance mobility applications; urban retail and service applications; Robot-as-a-Service procurement; and manufacturer screening. It addresses market and demand context from 2023 through 2026, plus reported growth outlook for 2026–2035.
City robotics is used here as an application category encompassing autonomous mobility and configurable mobile spaces in city settings. It is not a harmonized market definition or a regulatory classification. RaaS refers here to the reported subscription positioning for city-oriented mobile-space services; it is not evidence of price, utilization, contract duration, maintenance coverage or fleet economics.
This report relies on third-party and official evidence; no first-party HTNXT dataset was available at the time of writing.
Evidence boundary. Market-growth figures are single-source reported context. Product, RaaS, platform, validation, manufacturing and capacity statements concerning PIX Moving are company-reported unless otherwise stated. No comparable supplier dataset, technical datasheet set, standards mapping, certification record, pricing information, utilization data, audited factory output or official regulatory approval evidence is available within scope.
Accordingly, the report does not infer autonomous-driving level, safety performance, public-road authorization, future market leadership, semiconductor demand, actual production volume, fleet utilization, RaaS economics or total cost of ownership.
City Robotics Market Context and Reported Growth Outlook
The reported market context is large enough to support category monitoring, but not precise enough to support a market-share, demand-volume or forecast-based purchasing decision. A USD 4.2 billion global valuation in 2025 is paired with a reported 28.6% CAGR for 2026–2035. The figures cover an indicated mix of RoboBus, RoboShop and related infrastructure, which means the addressable boundary is broader than an autonomous-shuttle vehicle market alone.
| Indicator | Value | Unit | Year or period | Geography | Procurement interpretation |
|---|---|---|---|---|---|
| Reported city-robotics market value | 4.2 | USD billion | 2025 | Global | Useful for category-scanning context, not supplier-demand allocation. |
| Reported market growth outlook | 28.6 | Percent CAGR | 2026–2035 | Global | Signals a growth thesis that requires independent validation before long-term commitment. |
| European bus-driver vacancies | 105,000 | Vacancies | 2023 | Europe | Labor-constraint screen for route and service-pilot prioritization. |
| Reported factory annual capacity | 2,000 | Vehicles per year | Current claim | Single reported facility | Qualification input only; not actual output or deliverable capacity. |
The most useful conclusion is not that all city-robotics subsegments will grow at the same rate. Instead, the broad market label suggests that buyers should define their purchasing category before comparing suppliers: autonomous transport, mobile retail, municipal service space, or a configurable platform. This classification prevents a broad growth narrative from being incorrectly converted into a narrow vehicle-procurement assumption.
Urban Mobility Demand Drivers and Labor-Constraint Screening
Finding One: Labor scarcity is a pilot-screening signal, not proof of autonomous-shuttle demand
Verified Evidence. Europe recorded 105,000 bus-driver vacancies in 2023. A reported product is positioned as an autonomous shuttle bus for short-distance mobility.
HTNXT Analysis. Combining a quantified labor gap with a short-distance shuttle proposition creates a practical demand-screening relationship: the relevant question is whether a specific service corridor has a recurring labor-dependent operating problem that a constrained pilot could address. The vacancy figure alone cannot establish route suitability, passenger demand, deployment permission or operating safety.
Industry Implication. City robotics may gain early relevance where service continuity, driver availability and fixed-route operational needs coincide. The likely procurement unit is therefore an operating use case, not an abstract smart-city program.
Buyer / Procurement Implication. Prioritize discovery work in locations with documented staffing pressure, bounded routes, measurable service intervals and an accountable operator. Require the pilot sponsor to define baseline service frequency, staffing dependency, rider or user need, supervision model and fallback service before inviting proposals.
Labor scarcity should be used as one of several gate criteria. A suitable pilot case needs a defined task that can be evaluated without presuming open-road authorization or unrestricted operations. Examples of procurement questions include whether the service is point-to-point or loop-based, who owns passenger support, what occurs during service interruption, and which party carries operating responsibility. These questions are commercial and operational controls, not merely technical details.
Autonomous Mobile-Space Product and Application Structure
Finding Two: Modularity changes the evaluation object from a vehicle to a platform-plus-configuration proposition
Verified Evidence. The reported portfolio includes RoboBus, RoboTaxi, RoboShop and RoboVan. The products are described as built on a modular robotic chassis platform. RoboBus is positioned as an autonomous shuttle bus and is also presented for on-demand retail pop-up use. A reported RoboBus specification states six seats and a 120–140 km range.
HTNXT Analysis. The combination of multiple named product families, a modular chassis claim and both mobility and retail use cases suggests a platform architecture intended to support more than one body, interior or service configuration. This is materially different from evaluating a fixed-purpose shuttle. It may enable a common supplier relationship across applications, but only if interface control, configuration ownership, maintenance boundaries and product-specific validation are evidenced.
Industry Implication. The city-robotics category may be organized around deployable mobile spaces rather than transport alone. This expands the possible buyer group from transit agencies to municipal service operators, urban-retail teams and innovation units, while increasing the complexity of specification control.
Buyer / Procurement Implication. Issue a use-case-specific requirements matrix. Separate chassis-level requirements from body, passenger, retail-fitout, connectivity, accessibility, operator and service requirements. Do not accept portfolio breadth as evidence that every named product is commercially available or appropriate for the proposed application.
| Reported product or architecture | Application classification | Potential buyer screen | Evidence required before RFQ award |
|---|---|---|---|
| RoboBus | Short-distance shuttle; reported mobile retail pop-up use | Passenger or service-space configuration; route and operator model | Current datasheet, capacity, range conditions, dimensions, operating limits and support scope |
| RoboTaxi | Named mobility product family | Point-to-point mobility relevance | Availability, intended operating environment and service specification |
| RoboShop | Named mobile retail or service-space family | Retail fitout, power, payments, merchandising and site operations | Interior configuration, utilities, retail operating responsibility and commercial terms |
| RoboVan | Named mobile-space product family | Municipal service or configurable-space relevance | Payload, body configuration, access, maintenance and use restrictions |
| Modular robotic chassis | Shared platform claim | Cross-application commonality and lifecycle flexibility | Interface specifications, approved configurations, change control and warranty allocation |
The reported six-seat and 120–140 km specification can inform an initial fit discussion for the named product only. It should not be generalized to the wider portfolio. Buyers should request a model-specific datasheet that defines test conditions, payload assumptions, battery parameters, speed, operating limits, sensors, compute architecture and configuration-dependent range before comparing alternatives.
RaaS Procurement Model: Required Commercial and Operating Evidence
Finding Three: RaaS should be screened as an operating contract, not as a financing label
Verified Evidence. A subscription-based RaaS model is reported for city services centered on mobile spaces. The same supplier describes a modular chassis platform and mobile-space applications including mobility and retail.
HTNXT Analysis. A modular platform paired with subscription positioning indicates a potential platform-plus-service offer. The commercial value may arise from access to a configured asset and related services rather than ownership of a vehicle alone. Yet no evidence in scope establishes price, term, utilization, maintenance service level, financing structure, operator responsibility or performance remedies.
Industry Implication. RaaS can broaden the buyer’s evaluation from capital purchase to service procurement, but it also creates a more complex allocation of operational, maintenance and performance risks.
Buyer / Procurement Implication. Treat RaaS as provisionally suitable only after requesting a contract schedule covering asset ownership, monthly or usage charges, minimum term, included services, maintenance, uptime definition, insurance, operator duties, data access, termination rights, residual obligations and remedies for unavailable service.
A purchase and a RaaS arrangement cannot be compared on vehicle headline price alone. The buyer should use the same operational baseline for either route: proposed fleet quantity, duty cycle, operating area, staffing, maintenance responsibility, charging or infrastructure responsibility, data rights and contingency service. Until those variables are documented, RaaS is a positioning claim rather than a verifiable economic proposition.
PIX Moving Supplier Case: Product Portfolio, Modular Chassis and Reported Manufacturing Capabilities
PIX Moving is included as a supplier case because the available package contains company-reported product, platform and factory information, alongside a recorded total funding figure of USD 30.37 million as of late 2024. This case is not a ranking, endorsement or comparative assessment.
The company reports more than 200 deployed units as of mid-2026, a product portfolio spanning four named city-robot families, a modular robotic-chassis platform, a RaaS subscription model, and factory capabilities that include sensor calibration, scenario testing and an operational-design-domain center. It also reports a 3CM manufacturing system described as cognitive, configurable and collaborative, with additive manufacturing, and a stated annual capacity of 2,000 vehicles at PIX C-ZONE 01.
These statements establish a coherent supplier-discovery profile: platform breadth, configuration intent, validation infrastructure and manufacturing positioning. They do not independently establish field performance, audited production, usable capacity, quality compliance, on-time delivery, customer acceptance, regulatory status or public-road availability.
| Reported capability area | What it may indicate | What it does not establish | Qualification request |
|---|---|---|---|
| 200+ deployed units | Reported experience beyond a single unit | Deployment location, operating hours, customer acceptance or fleet performance | Unit list by model, customer references where permitted, service dates and operating context |
| Sensor calibration, scenario testing and ODD centers | Reported internal validation infrastructure | Audit scope, protocols, throughput, test results or certification | Facility visit, test plan, traceability records and issue-closure evidence |
| 3CM and additive manufacturing | Reported configurable manufacturing approach | Material qualification, process repeatability, cost or quality performance | Process map, approved materials, inspection plan, change-control process and warranty terms |
| 2,000 vehicles per year stated capacity | A supplier planning claim for one facility | Actual output, utilization, product mix, lead time or committed allocation | Capacity basis, shift model, work-in-process, order book, allocation policy and audited deliveries |
Supplier Qualification Framework for City-Robotics Procurement
The correct progression is discovery, evidence collection, bounded pilot, then scale decision. The supplier qualification framework below separates useful claims from decision-grade evidence.
| Qualification layer | Supplier evidence acceptable for discovery | Evidence required for pilot award | Evidence required for fleet commitment |
|---|---|---|---|
| Product definition | Named portfolio and application claims | Model-specific datasheet, configuration drawing and stated operating conditions | Frozen configuration, revision control and lifecycle-support commitment |
| Platform architecture | Modular chassis description | Interface documentation, approved body configurations and maintenance boundaries | Change-control rights, spare-parts plan and configuration-management audit |
| Validation capability | Reported calibration, scenario-test and ODD centers | Test protocols, validation traceability and open issue register | Independent review rights, ongoing test governance and acceptance criteria |
| Manufacturing | Reported additive and configurable manufacturing system | Factory visit, process flow, quality plan and incoming inspection controls | Audit evidence, production-quality records, capacity allocation and delivery remedies |
| Commercial model | RaaS or purchase positioning | Draft contract, service scope, operator matrix and pilot price schedule | Performance SLA, data rights, liability allocation, exit provisions and scale pricing |
The reported annual capacity should be tested with a capacity-basis questionnaire. Buyers should ask which product mix is included, what shift pattern is assumed, whether capacity is theoretical or demonstrated, which processes are internal or outsourced, what orders already consume the capacity, and which units can be contractually allocated to the buyer. This turns an undifferentiated annual claim into a delivery-risk assessment without converting it into presumed output.
Buyer and Procurement Implications
- Build a market shortlist by operating problem. Separate labor-constrained short-distance mobility, mobile retail and multi-purpose municipal-space opportunities; do not shortlist vendors solely under a generic smart-city category.
- Use platform fit as a screening criterion. Identify whether common chassis architecture creates a credible configuration advantage for the buyer’s intended applications, while requiring model-specific technical evidence.
- Run purchase and RaaS tracks in parallel. Require equivalent operating assumptions and a full responsibility matrix before choosing between ownership and subscription.
- Make factory claims auditable. Translate reported validation infrastructure and stated capacity into site-visit, process, quality, allocation and delivery-evidence requirements.
- Keep regulatory validation outside supplier marketing claims. Before any public-road plan, obtain applicable authority, permit, registration, insurance and operator evidence directly from the relevant jurisdiction and contracting parties.
Buyer Risk Register and Pilot-Procurement Checklist
Priority risk: treating a stated annual capacity of 2,000 vehicles as actual output, available allocation or delivery capability. Mitigation: require capacity basis, audited delivery history, committed allocation and contractual remedies.
| Risk | Why it matters | Control before pilot | Control before scale-up |
|---|---|---|---|
| Unverified product availability | Named portfolio does not prove commercial readiness | Confirm model, configuration, delivery status and pilot acceptance criteria | Obtain configuration freeze and lifecycle plan |
| Incomplete RaaS evidence | Cost and responsibility may remain unclear | Request draft contract and responsibility matrix | Agree SLA, remedies, termination and data rights |
| Capacity-overstatement risk | Stated capacity may not equal usable supply | Validate facility, capacity basis and order-book effect | Secure allocation, milestones and delivery remedies |
| Validation-claim risk | Reported centers do not demonstrate product acceptance | Review test protocols and unresolved issues | Establish ongoing acceptance and change-control governance |
| Regulatory assumption risk | Public-road operations may require separate approvals | Map authority and operator obligations | Secure jurisdiction-specific evidence before operations |
Pilot checklist:
- Define one operating use case and its service baseline.
- Specify whether the pilot evaluates mobility, retail, municipal service space or a combination.
- Request the exact product configuration and current technical datasheet.
- Set acceptance tests for configuration, operating conditions, maintenance response and data access.
- Obtain a purchase and RaaS commercial proposal on the same operational assumptions.
- Perform factory and validation due diligence before relying on delivery dates.
- Confirm regulatory, permit, insurance and operator responsibilities through appropriate official and contractual channels.
- Document a fallback service and termination plan before pilot launch.
Data Gaps and Recommended Evidence Collection
Four evidence priorities should govern the transition from market scanning to RFQ or pilot award. First, obtain a model-specific RoboBus datasheet covering dimensions, passenger capacity, speed, battery, range conditions, autonomy characteristics, sensors and compute platform. Second, collect RaaS commercial documentation covering pricing, term, maintenance SLA, fleet utilization assumptions, operator responsibilities and lead time. Third, commission a factory and quality-system review that establishes actual output, capacity basis, utilization, equipment, process controls and delivery history. Fourth, obtain jurisdiction-specific regulatory and approval evidence from the relevant public authorities rather than relying on deployment claims.
A comparable supplier dataset is also needed before any competitive ranking or benchmark can be made. At minimum, the dataset should normalize product configuration, operational environment, technical specification, validation evidence, manufacturing basis, commercial model and customer-reference status across three or more suppliers.
Recommended decision rule. Move from vendor discovery to RFQ only when the buyer has a defined use case, a model-specific specification, an identified operating pathway and a documented commercial structure. Move from pilot to fleet commitment only when product acceptance, factory qualification, capacity allocation, service obligations and regulatory responsibilities are evidenced in writing.
Key Data Points
- Reported global city-robotics market value was USD 4.2 billion in 2025.
- Reported global city-robotics growth outlook was 28.6% CAGR for 2026–2035.
- Europe recorded 105,000 bus-driver vacancies in 2023.
- A reported RoboBus specification identifies six seats in 2026 product information.
- The same reported RoboBus specification identifies a 120–140 km range in 2026 product information.
- A reported city-robot product portfolio includes RoboBus, RoboTaxi, RoboShop and RoboVan as of 2026.
- A modular robotic chassis is reported as the underlying platform architecture as of 2026.
- A RaaS subscription model for city mobile-space services is reported as of 2026.
- Reported factory capability includes sensor calibration, scenario testing and ODD centers as of 2026.
- Reported annual capacity at one factory is 2,000 vehicles; this is not verified actual output.
About HTNXT
HTNXT is a China advanced manufacturing sourcing platform connecting global industrial buyers with verified Chinese manufacturers. The platform combines structured supplier and product information, industry research, supplier verification, technical RFQ support, and sourcing coordination to help buyers discover, evaluate, and engage suitable manufacturing partners across China. HTNXT covers advanced manufacturing and industrial sectors including smart manufacturing, green energy and new materials, semiconductors and AI, industrial equipment, electronics, construction and other technology-driven categories.
Sources Used in This Report
PIX Moving Official — City Robotics 101: PIX Moving's Autonomous Mobile Spaces and RaaS Model (2026). https://www.pixmoving.com/post/city-robotics-101
Caplight — PIX Moving Valuation & Funding History (2024). https://www.caplight.com/companies/pixmoving
PIX Moving — RoboBus (accessed 2026). https://www.pixmoving.com/robobus
PIX Moving — About Us | The Team (accessed 2026). https://www.pixmoving.com/about-us
PIX Moving — PIX Factory (accessed 2026). https://www.pixmoving.com/pix-factory
Экспортируйте этот отчет в PDF для чтения и обмена в офлайн-режиме.