Hermelin C-UAS: Product launch in Germany

Development and reported outcome

On 15-Jun-26, Rheinmetall unveiled, upgraded or advanced Hermelin C-UAS under Hermelin C-UAS, targeting German / NATO defense customers — target users.

Reporting limitation: the milestone is treated as product/technology maturation unless a separate customer order is disclosed.[S1]

Program, platform and stakeholders

Programme or contract: Hermelin C-UAS. Platform or product: Hermelin C-UAS. Recorded supplier, developer or relevant organization: Rheinmetall (reported headquarters/country: Germany). Recorded customer, operator or intended user: German / NATO defense customers — target users (reported headquarters/country: Germany / NATO).[S1]

Mission and technical scope

The following are classifications recorded in the source master, not additional claims of operational deployment: Mission/use-case classification: Counter-UAS; Patrol / Force Protection; Base / Perimeter Security. Mobility classification: Wheeled. Operating mode: Remote / Autonomous-capable.

Contract, value and shipment signals

Recorded quantity, delivery, demonstration or volume signal: Demonstrator; quantity not disclosed. Delivery schedule, procurement window or milestone status: Product launched at Eurosatory 2026; no production order disclosed.[S1]

Source verification and interpretation limits

UXV Searcher master source-coverage note: First-party product-launch source retained.

Interpretation boundary: A product launch does not, by itself, establish paid orders or operational deliveries.[S1]

UXV Searcher analysis — what the development changes

UXV Searcher interpretation — product unveiling / launch: The Germany UGV record for Hermelin C-UAS is best treated as a product availability signal. A launch broadens the visible product offering but does not, without buyer evidence, establish demand or market penetration.

Traceability for buyers: The dataset associates Rheinmetall with German / NATO defense customers — target users for Hermelin C-UAS. This supports stakeholder mapping; supply-chain tier, exclusivity and signed-customer relationships need the underlying source before firm classification.

Client-use interpretation: For intelligence users tracking Counter-UAS; Patrol / Force Protection; Base / Perimeter Security, the relevant next proof points are ground mobility, autonomy, payload integration and field acceptance. Seek customer orders, reliable specifications, deliveries and repeat purchases rather than counting exhibited units as sales.[S1]

Quantitative evidence, calculations and limits

Quantity/scope signal: Demonstrator; quantity not disclosed. Counting rule: Scope or component count; not a count of procured or delivered unmanned platforms. Delivery/timing evidence: Product launched at Eurosatory 2026; no production order disclosed. Scheduling language is not independently proof of completion or acceptance.

Keep reported, derived and prospective quantities separate; do not convert activity into installed-base counts without a shipment or acceptance source.[S1]