SABUVIS II: Development milestone in Poland — 07 Feb 2026 — SABUVIS II coordinated AUV swarm

Development and reported outcome

On February 7, 2026, the Poland-led SABUVIS II defence research project completed its second stage after four years of work on coordinated autonomous-underwater-vehicle swarms. The program developed underwater communications, common command-and-control, and coordinated mission execution for surveillance, infrastructure protection, and harbour-security scenarios. The EUR 3.7 million figure is the overall EDA-managed R&D project budget and must not be treated as Polish UUV procurement revenue.[S1] [S2]

Program, platform and stakeholders

Programme or contract: SABUVIS II. Platform or product: SABUVIS II coordinated AUV swarm. Platform classification: Autonomous Operated Vehicle. Recorded supplier, developer or relevant organization: European Defence Agency / Polish Naval Academy (reported headquarters/country: Belgium / Poland). Recorded customer, operator or intended user: Participating European defense organizations (reported headquarters/country: Poland / EU participants).[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: Swarm / Collaborative Autonomy; Underwater ISR / Surveillance; Critical Underwater Infrastructure Protection; Harbor / Base Defense.

Contract, value and shipment signals

Original reported amount or scope: EUR 3,700,000 total project budget. Original-currency label: EUR. USD figure or conversion stated in the master: Approx. USD 4.36 million analyst conversion. No additional FX conversion has been generated for this brief. Delivery schedule, procurement window or milestone status: Project completed. Recorded contractual start: 8-Feb-22. Recorded contractual end: 7-Feb-26. Recorded contractual duration: 4 years.[S1] [S2]

Source verification and interpretation limits

UXV Searcher master source-coverage note: Łukasiewicz-PIAP gives the project period as 08-Feb-2022 through 07-Feb-2026, supporting the exact completion date. EDA independently confirms conclusion in early February 2026, Poland as lead nation, and the EUR 3.7 million total R&D budget. The budget is not Polish UUV procurement revenue.

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 Poland UUV record for SABUVIS II 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 European Defence Agency / Polish Naval Academy with Participating European defense organizations for SABUVIS II coordinated AUV swarm. 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 Swarm / Collaborative Autonomy; Underwater ISR / Surveillance; Critical Underwater…, the relevant next proof points are underwater mission readiness, subsea navigation and operator acceptance. Watch for successful acceptance testing, commercial availability, customer commitments and quantified deliveries.[S1] [S2]

Quantitative evidence, calculations and limits

Financial signal (master transcription): EUR 3,700,000 total project budget. Classification: Tender estimate, ceiling or budget, not necessarily an awarded or paid amount. Delivery/timing evidence: Project completed. Scheduling language is not independently proof of completion or acceptance. Reproducible calculations: Recorded start-to-end calendar interval: 1,460 days ((2026-02-07) - (2022-02-08) = 1460 elapsed calendar days). 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]