PIAP HUNTeR + AREX remote weapon system: Development milestone in Poland

Development and reported outcome

On 1-Mar-26, Łukasiewicz-PIAP / WB Group–AREX unveiled, upgraded or advanced PIAP HUNTeR + AREX remote weapon system under BoHun, targeting Polish Armed Forces / MON via NCBR PERUN.

Reporting limitation: the milestone is treated as product/technology maturation unless a separate customer order is disclosed.[S1]

Program, platform and stakeholders

Programme or contract: BoHun. Platform or product: PIAP HUNTeR + AREX remote weapon system. Recorded supplier, developer or relevant organization: Łukasiewicz-PIAP / WB Group–AREX (reported headquarters/country: Poland). Recorded customer, operator or intended user: Polish Armed Forces / MON via NCBR PERUN (reported headquarters/country: Poland).[S1]

Mission and technical scope

The following are classifications recorded in the source master, not additional claims of operational deployment: Mission/use-case classification: Combat / fire support; manned-unmanned teaming. Mobility classification: Wheeled. Operating mode: Remote / Autonomous-capable.

Contract, value and shipment signals

Original reported amount or scope: PLN 26,242,068 funding. Original-currency label: PLN. Recorded quantity, delivery, demonstration or volume signal: Prototype programme; number not disclosed. Delivery schedule, procurement window or milestone status: Development through Mar-2028. Recorded contractual start: 1-Mar-26. Recorded contractual end: 1-Mar-28. Recorded contractual duration: 24 months.[S1]

Source verification and interpretation limits

UXV Searcher master source-coverage note: Funded R&D/prototype programme. The amount is project funding, not vehicle procurement value.

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

UXV Searcher analysis — what the development changes

UXV Searcher interpretation — product or engineering development: The Poland UGV record for BoHun 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 Łukasiewicz-PIAP / WB Group–AREX with Polish Armed Forces / MON via NCBR PERUN for PIAP HUNTeR + AREX remote weapon system. 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 Combat / fire support; manned-unmanned teaming, the relevant next proof points are weapons/payload integration, safety approval and deployability. Watch for successful acceptance testing, commercial availability, customer commitments and quantified deliveries.[S1]

Quantitative evidence, calculations and limits

Financial signal (master transcription): PLN 26,242,068 funding. Classification: Financial context as recorded in the master; scope and contract status must follow the underlying source. Quantity/scope signal: Prototype programme; number not disclosed. Counting rule: Scope or component count; not a count of procured or delivered unmanned platforms. Delivery/timing evidence: Development through Mar-2028. Scheduling language is not independently proof of completion or acceptance. Reproducible calculations: Recorded start-to-end calendar interval: 731 days ((2028-03-01) - (2026-03-01) = 731 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]