The direct answer
What is supported? Ouster's 2026 second-quarter exhibit says the company shipped more than 17,000 lidar and camera units for revenue, with lidar at approximately 53% of the combined quantity. The quarter ended 2026-06-30, and both the 10-Q and furnished earnings exhibit were filed on 2026-08-06.
How many lidar units was that? The filing does not say exactly. “More than 17,000” and “approximately 53%” are both inexact. Multiplying them can produce a rough illustration, but not a defensible exact shipment count. RCI therefore publishes the threshold and approximate share exactly as bounded.
Did RCI verify product performance or customer deployments? No. RCI fixed and hashed the two SEC-hosted documents, traced twelve observations, audited ten missing-field boundaries and recomputed one revenue ratio. It handled zero Ouster sensors, cameras, chips or software workloads.
The filing is useful evidence that Ouster's quarterly commercial volume now combines substantial lidar and camera shipments. It cannot establish exact lidar units, model adoption, market share, customer success, safety, reliability or performance.
The 53% share cannot be turned into an exact unit count
| Published field | Value | Evidence role | Boundary |
|---|---|---|---|
| Combined units | >17,000 | Issuer-reported historical fact | Lidar and cameras combined; no exact count |
| LiDAR share | Approximately 53% | Issuer-reported approximation | Not an exact lidar quantity or market share |
| Model split | Not disclosed | RCI missing-field finding | No OS, DF, Rev7, Rev8, ZED or other model table |
| Customer/application split | Not disclosed | RCI missing-field finding | No customer-level robot deployment can be inferred |
The company describes the units as shipped “for revenue.” That wording is narrower than production, orders, bookings or installed base. Units produced but not recognized for revenue, canceled orders and customer deployment status are not covered by the disclosed quantity.
Product revenue is broad—not lidar revenue
The 10-Q reports $54.626 million in total revenue and $52.763 million in product revenue for the quarter. RCI divides those rounded values to obtain 96.59%. That is a transparent arithmetic result, not a company-reported percentage.
Product revenue includes lidar sensors, cameras and AI compute systems. Ouster completed its acquisition of Stereolabs on 2026-02-04, so the quarter also includes acquired vision and compute products that had no comparable contribution in the prior-year period. Neither $52.763 million nor the 96.59% ratio is a lidar-revenue figure.
The filing reports year-over-year revenue growth of 56%, attributing it primarily to increased sensor volumes and partly to acquired Stereolabs products, while lower average selling prices offset some growth. It discloses direction but no exact blended or model-level ASP.
Commitments are a supply signal, not a shipment forecast
As of 2026-06-30, Ouster reported approximately $24.8 million in non-cancelable commitments to third-party contract manufacturers and approximately $21.5 million to other vendors. The filing also identifies Benchmark Electronics, Fabrinet and other suppliers as dependencies.
Those amounts show company-level procurement exposure. They do not identify components, product families, delivery schedules or future revenue. They should not be used to estimate how many lidar sensors will ship in a later quarter.
The reported 49% GAAP gross margin also needs context: cost of revenue included a $5.4 million reduction associated with IEEPA import-duty refunds. RCI does not treat 49% as a normalized component-cost baseline.
“In-house testing” is not a public benchmark
The 10-Q says Ouster announced its Rev8 family and that its Chronos chip had been fabricated by the foundry partner and was undergoing in-house testing. This is a dated roadmap-status disclosure.
The filing attaches no Chronos test protocol, raw output, production-qualification matrix, independent result or commercial-availability date. RCI therefore records “fabricated; undergoing in-house testing” without converting it into a performance, readiness or availability claim.
What an engineering-grade supply record still needs
- Exact quantities: exact lidar and camera units rather than a threshold and approximate mix.
- Model identity: OS, DF, Rev8, ZED or other orderable-model allocation.
- Application boundary: robotics, industrial, automotive and smart-infrastructure quantities mapped to stated use cases.
- Commercial boundary: region, channel, customer concentration and ASP without exposing confidential customers.
- Validation boundary: public protocols and raw results for new chip or sensor performance statements.
Ten disclosure checks
| Field | Status | Evidence | Boundary |
|---|---|---|---|
| fixed filing identity | disclosed | Two accession numbers, URLs, byte counts and audit-date SHA-256 digests are recorded. | The hashes identify the downloaded SEC HTML bytes, not the complete filing package. |
| exact total sensor units | not-disclosed | The exhibit says more than 17,000 units. | RCI does not replace a threshold with 17,000 or another exact number. |
| exact lidar units | not-disclosed | LiDAR is described as approximately 53% of the combined greater-than total. | Multiplication cannot produce an exact lidar count from two inexact inputs. |
| model level shipments | absent | No OS, DF, Rev7, Rev8, ZED or other model shipment table is supplied. | The filing cannot rank products or establish model adoption. |
| customer and geographic mix | insufficient-for-sensor-attribution | Company-level geography and customer concentration disclosures do not map shipments to models. | No customer-level robot deployment or regional lidar-unit count is inferred. |
| average selling price | direction-only | The filing says lower ASPs partly offset volume-driven growth. | No exact blended or model-level ASP is disclosed. |
| manufacturing commitments | company-level | $24.8 million to contract manufacturers and $21.5 million to other vendors are disclosed. | Commitments are not component demand, deliveries or revenue forecasts. |
| roadmap validation | not-publicly-demonstrated | Chronos is described as fabricated and in in-house testing. | No public raw result, qualification matrix or independent test is attached. |
| independent product validation | not-performed | RCI reviewed issuer filings and recomputed one ratio only. | Zero Ouster sensors, cameras, chips or software workloads were tested by RCI. |
| market share or investment conclusion | out-of-scope | The sources describe one issuer's quarter. | No market-size, competitor, valuation, safety or procurement conclusion is supported. |
Method, work level and rights
RCI fixed the two SEC accessions, downloaded the primary HTML documents with an identifying user agent, recorded byte counts and SHA-256 digests, traced each observation to a filing section and recomputed only product revenue divided by total revenue. No filing prose, image or table is reproduced. Historical facts, approximations, forward-looking statements and RCI derivations remain separately labeled.
Highest completed work level: EV3 public-data recomputation. The EV3 label applies to the 96.59% ratio computed from disclosed GAAP values. The page also includes EV1 source verification and audit-date hashes. It includes no EV4 physical bench test, EV5 external replication or EV6 accredited-laboratory result. See the evidence work levels.
- All operational and roadmap facts originate with Ouster and are not independent validation.
- The combined shipment threshold and approximate lidar share do not reveal an exact lidar count.
- Stereolabs products make current-period comparisons broader than lidar alone.
- The filing provides no model-level shipment, revenue, ASP, customer or application table.
- RCI performed zero hardware, firmware, software, manufacturing or market-share tests.
Primary sources: Ouster Form 10-Q and Form 8-K Exhibit 99.1. RCI publishes independently worded facts, source metadata and analysis; it does not mirror the filing prose, images or tables.
Download the supply-signal data
Download the immutable JSON release and record-level CSV. Stable aliases are current JSON and current CSV.
Suggested citation: Robot Component Index. “Ouster Q2 2026 LiDAR Supply Signal: >17,000 Sensor Units, ~53% LiDAR, Zero Model-Level Split.” RCI 041, version 0.1.0, 2026-08-11. https://robotcomponentindex.com/research/ouster-q2-2026-lidar-supply-signal/
For version-aware BibTeX and machine citation records, use Cite RCI.