EUROGUARD / Medium-sized Semi-Autonomous Surface Vessel: Development milestone in Denmark

Development and reported outcome

EUROGUARD held its Critical Design Review and presented the physical hull of its 45 m semi-autonomous naval prototype at Baltic Workboats' Nasva shipyard on May 21. Baltic Workboats is the project coordinator and prototype builder; Danish OMT and SH Defence are consortium participants. The €95 million program runs from 2023 to 2027 and covers surveillance, mine countermeasures, drone operations and other naval missions.[S1] [S2]

Program, platform and stakeholders

Programme or contract: EUROGUARD / Medium-sized Semi-Autonomous Surface Vessel. Platform or product: 45 m EUROGUARD modular semi-autonomous surface vessel prototype. Platform classification: Large (>24 m; 45 m). Recorded supplier, developer or relevant organization: OMT (reported headquarters/country: Denmark). Recorded customer, operator or intended user: EU Member State defense participants / future European navies (reported headquarters/country: European Union).[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: Multi-Mission Naval Operations; System-of-Systems Integration. Operating mode: Autonomous Surface Vessel (ASV).

Contract, value and shipment signals

Original reported amount or scope: EUR 95 million total program budget; EUR 65 million EDF funding. Original-currency label: EUR. Recorded quantity, delivery, demonstration or volume signal: 1 prototype. Delivery schedule, procurement window or milestone status: Prototype completion/testing planned later in program. Recorded contractual start: Existing EDF project. Recorded contractual end: Planned completion 2027. Recorded contractual duration: Multi-year.[S1] [S2]

Source verification and interpretation limits

UXV Searcher master source-coverage note: Baltic Workboats' official source identifies the Estonian company as EUROGUARD project coordinator and confirms the May 21 CDR, 45 m prototype and €95 million program. Danish OMT/SH Defence participation does not change the lead-HQ test.

Interpretation boundary: A development milestone does not by itself establish completion, acceptance or fleet induction.[S1] [S2]

UXV Searcher analysis — what the development changes

UXV Searcher interpretation — product or engineering development: The Denmark USV record for EUROGUARD / Medium-sized Semi-Autonomous Surface Vessel is best treated as a technical progression signal. The record documents a capability step or integration scope, not proof of mass production or repeatable sales.

Traceability for buyers: The dataset associates OMT with EU Member State defense participants / future European navies for 45 m EUROGUARD modular semi-autonomous surface vessel prototype. 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 Multi-Mission Naval Operations; System-of-Systems Integration, the relevant next proof points are marine mission suitability, payload integration and measurable delivery or service outcomes. Watch for successful acceptance testing, commercial availability, customer commitments and quantified deliveries.[S1] [S2]

Quantitative evidence, calculations and limits

Financial signal (master transcription): EUR 95 million total program budget; EUR 65 million EDF funding. Classification: Programme or funding envelope; not a signed platform order or unit price. Quantity/scope signal: 1 prototype. Counting rule: Scope or component count; not a count of procured or delivered unmanned platforms. Delivery/timing evidence: Prototype completion/testing planned later in program. Scheduling language is not independently proof of completion or acceptance. Reproducible calculations: EDF funding share of total EUROGUARD budget: 68.4% (65 / 95 × 100 = 68.4%). Refer to the calculation cards for assumptions and limitations.

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