Portsmouth LNTM 27/26: United Kingdom test and trial record

Development and reported outcome

KHM Portsmouth authorized remotely controlled RATTLER USV operations covering trials and training. The notice establishes an authorized window but does not prove every planned evolution occurred.[S1] [S2]

Program, platform and stakeholders

Programme or contract: Portsmouth LNTM 27/26. Platform or product: RATTLER 1-7. Recorded supplier, developer or relevant organization: Royal Navy (reported headquarters/country: United Kingdom). Recorded customer, operator or intended user: Royal Navy / trial organization not disclosed (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: Technology Demonstration / Testbed. Operating mode: Remotely Operated Surface Vessel (ROSV).

Contract, value and shipment signals

Recorded quantity, delivery, demonstration or volume signal: Up to seven RATTLER callsigns/designations; distinct hull count not confirmed. Delivery schedule, procurement window or milestone status: Through 31-Mar-26. Recorded contractual start: 15-Dec-25. Recorded contractual end: 31-Mar-26.[S1] [S2]

Source verification and interpretation limits

UXV Searcher master source-coverage note: Deep verified: Portsmouth LNTM 27/26 was issued Jan. 1 and covers RATTLER 1-7 remote-control operations through Mar. 31. The callsigns do not prove seven distinct hulls, so vessel quantity is not fixed at seven.

Interpretation boundary: Testing, authorization and demonstrations should not be counted as confirmed purchases or fleet deliveries without a separate acceptance source.[S1] [S2]

UXV Searcher analysis — what the development changes

UXV Searcher interpretation — validation / operational testing: The United Kingdom USV record for Portsmouth LNTM 27/26 is best treated as a technical maturity signal. Testing, demonstration and certification-type activity can reduce integration uncertainty but is not equivalent to contracted fleet deployment.

Traceability for buyers: The dataset associates Royal Navy with Royal Navy / trial organization not disclosed for RATTLER 1-7. 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 Technology Demonstration / Testbed, the relevant next proof points are marine mission suitability, payload integration and measurable delivery or service outcomes. Monitor test result, qualification scope, operational acceptance and subsequent paid orders.[S1] [S2]

Quantitative evidence, calculations and limits

Quantity/scope signal: Up to seven RATTLER callsigns/designations; distinct hull count not confirmed. Counting rule: Trial/deployment context; not necessarily procurement or paid fleet additions. Delivery/timing evidence: Through 31-Mar-26. Scheduling language is not independently proof of completion or acceptance. Reproducible calculations: Recorded start-to-end calendar interval: 106 days ((2026-03-31) - (2025-12-15) = 106 elapsed calendar days). Refer to the calculation cards for assumptions and limitations.

Trial participation and travelled distance describe testing activity, not sales volumes.[S1] [S2]