Project Beehive – All 20 USVs Delivered: Programme announcement in United Kingdom

Development and reported outcome

BMT reported that all 20 Project Beehive USVs had been delivered to the Royal Navy by June 23, closing the delivery sequence. Training, C2 evaluation and experimentation remain separate lifecycle stages.[S1] [S2]

Program, platform and stakeholders

Programme or contract: Project Beehive – All 20 USVs Delivered. Platform or product: 20 Project Beehive / K3 Scout-spec USVs. Platform classification: Medium (K3 Scout: 8.4 m). Recorded supplier, developer or relevant organization: Kraken Technology Group (reported headquarters/country: United Kingdom). Recorded customer, operator or intended user: Royal Navy (reported headquarters/country: United Kingdom).[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: Training / Combat Readiness. Operating mode: Autonomous Surface Vessel (ASV).

Contract, value and shipment signals

Original reported amount or scope: Included in GBP 10.25 million ex-VAT Project Beehive award; no new delivery value. Original-currency label: GBP. Recorded quantity, delivery, demonstration or volume signal: 20 total delivered by Jun. 23 publication. Delivery schedule, procurement window or milestone status: Completed by 23-Jun-26.[S1] [S2]

Source verification and interpretation limits

UXV Searcher master source-coverage note: Deep verified: BMT stated by Jun. 23 that all 20 Project Beehive USVs had been delivered, following Parliament's Jun. 9 status of 18 delivered. The fleet is covered by the existing GBP 10.25 million ex-VAT award; no new delivery value is created.[S1] [S2]

UXV Searcher analysis — what the development changes

UXV Searcher interpretation — reported dispatch or deployment update: The United Kingdom USV record for Project Beehive – All 20 USVs Delivered is best treated as a fulfilment progress signal. The evidence is useful for tracking execution against prior commitments; it must not be counted as a new contract simply because the delivery was reported now.

Traceability for buyers: The dataset associates Kraken Technology Group with Royal Navy for 20 Project Beehive / K3 Scout-spec USVs. 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 Training / Combat Readiness, the relevant next proof points are mission validation, safety standards and production commitments. Reconcile dispatched, received, accepted and active-service quantities against the parent order before updating fleet totals.[S1] [S2]

Quantitative evidence, calculations and limits

Financial signal (master transcription): Included in GBP 10.25 million ex-VAT Project Beehive award; no new delivery value. Classification: Financial context as recorded in the master; scope and contract status must follow the underlying source. Quantity/scope signal: 20 total delivered by Jun. 23 publication. Counting rule: Reported delivery-stage quantity; acceptance and active fleet use need separate evidence. Delivery/timing evidence: Completed by 23-Jun-26. 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]