Hanwha Systems 30-ton USV Development: Product launch in South Korea

Development and reported outcome

Hanwha Systems launched its 30-ton-class combat USV in early June 2026, completing the first physical prototype milestone before sea trials. The platform is part of Hanwha's broader autonomous maritime development portfolio. Hanwha's roughly KRW 70 billion self-investment covers both 30-ton and 140-ton USV programs and is not assigned solely to this prototype.[S1] [S2]

Program, platform and stakeholders

Programme or contract: Hanwha Systems 30-ton USV Development. Platform or product: 30-ton-class combat USV. Recorded supplier, developer or relevant organization: Hanwha Systems (reported headquarters/country: South Korea). Recorded customer, operator or intended user: No procurement customer disclosed (reported headquarters/country: South Korea).[S1] [S2]

Mission and technical scope

The following are classifications recorded in the source master, not additional claims of operational deployment: Mission/use-case classification: Autonomous Naval Operations. Operating mode: Autonomous Surface Vessel (ASV).

Contract, value and shipment signals

Original reported amount or scope: KRW 70 billion combined self-investment for 30-ton and 140-ton USV development. Original-currency label: KRW. USD figure or conversion stated in the master: USD 46.64 million combined (source-reported equivalent). No additional FX conversion has been generated for this brief. Recorded quantity, delivery, demonstration or volume signal: 1 USV. Delivery schedule, procurement window or milestone status: Successfully launched in early June; exact day not disclosed.[S1] [S2]

Source verification and interpretation limits

UXV Searcher master source-coverage note: Hanwha and Yonhap confirm one 30-ton-class USV was launched in early June and moved into autonomous-navigation testing. Hanwha's approximately KRW 70 billion self-investment covers both the 30-ton and 140-ton USV programs, so the amount is recorded here as a broader combined development investment and is not attributable solely to this prototype.

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

UXV Searcher analysis — what the development changes

UXV Searcher interpretation — product unveiling / launch: The South Korea USV record for Hanwha Systems 30-ton USV Development 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 Hanwha Systems with No procurement customer disclosed for 30-ton-class combat USV. 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 Autonomous Naval Operations, the relevant next proof points are marine mission suitability, payload integration and measurable delivery or service outcomes. Seek customer orders, reliable specifications, deliveries and repeat purchases rather than counting exhibited units as sales.[S1] [S2]

Quantitative evidence, calculations and limits

Financial signal (master transcription): KRW 70 billion combined self-investment for 30-ton and 140-ton USV development. Classification: Facility/investment figure, not unmanned-vehicle sales or shipments. USD value qualifier: USD 46.64 million combined (source-reported equivalent). This is preserved from the workbook and has not been independently converted or assigned to equipment beyond the master’s stated scope. Quantity/scope signal: 1 USV. Counting rule: Reported quantity or scope; article-level stage classification determines whether it is a platform, service, component or prospective count. Delivery/timing evidence: Successfully launched in early June; exact day not 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] [S2]