MFP-1 Delivery to Denmark DALO: Programme announcement in Denmark

Development and reported outcome

On 6-Jan-26, XRC Robotics delivered or operationally fielded MFP-1 for Danish Ministry of Defence Acquisition and Logistics Organisation / Royal Danish Army under MFP-1 Delivery to Denmark DALO.[S1]

Program, platform and stakeholders

Programme or contract: MFP-1 Delivery to Denmark DALO. Platform or product: MFP-1. Recorded supplier, developer or relevant organization: XRC Robotics (reported headquarters/country: United Kingdom). Recorded customer, operator or intended user: Danish Ministry of Defence Acquisition and Logistics Organisation / Royal Danish Army (reported headquarters/country: Denmark).[S1]

Mission and technical scope

The following are classifications recorded in the source master, not additional claims of operational deployment: Mission/use-case classification: ISR / Reconnaissance; tactical experimentation. Operating mode: Remote / Autonomous-capable.

Contract, value and shipment signals

Recorded quantity, delivery, demonstration or volume signal: 4 delivered. Delivery schedule, procurement window or milestone status: Delivered by 06-Jan-2026.[S1]

Source verification and interpretation limits

UXV Searcher master source-coverage note: Distinct delivery stage within the Jan 8-UGV THeMIS/MFP-1 test family. Keep as a development milestone; count the procurement/test family once in KPIs.[S1]

UXV Searcher analysis — what the development changes

UXV Searcher interpretation — reported dispatch or deployment update: The Denmark UGV record for MFP-1 Delivery to Denmark DALO 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 XRC Robotics with Danish Ministry of Defence Acquisition and Logistics Organisation / Royal Danish Army for MFP-1. 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 ISR / Reconnaissance; tactical experimentation, the relevant next proof points are ground mobility, autonomy, payload integration and field acceptance. Reconcile dispatched, received, accepted and active-service quantities against the parent order before updating fleet totals.[S1]

Quantitative evidence, calculations and limits

Quantity/scope signal: 4 delivered. Counting rule: Reported delivery-stage quantity; acceptance and active fleet use need separate evidence. Delivery/timing evidence: Delivered by 06-Jan-2026. 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]