HDF Logistics Fleet // Technical Readout
TUC-5
Field Procurement Archive
The last stretch between organized logistics and the fighting unit. Not a small LUT-10 and not a cut-rate CVT-20 — a distinct vehicle for ammunition to firing positions, water and batteries and field tools forward, drone kit and repair parts to wherever the unit actually is right now. Small enough to go where a convoy truck shouldn't. Useful enough to be everywhere. Commanders send it when speed and flexibility matter more than gross capacity, the route is poor, or a full logistics truck would be too large or too exposed for the job.
Engineering / In-universe Specification
Engineering Assessment
The overlap is superficial — both are Valessan, both are wheeled logistics platforms, both haul cargo. But the LUT-10 is a standardized convoy truck built for volume, while the TUC-5 is built to follow a fighting unit into terrain a convoy truck has no business entering. Deploy it as “LUT-10, but cheaper” and it becomes redundant. Deploy it as last-leg unit support and it fills a gap nothing else in the fleet covers.
This is the line that has to stay clean, especially now that the CVT-20 exists as the fleet's actual armored vehicle. The TUC-5's reinforced cab survives fragments, debris, and weather — it is not rated to trade direct fire, and doctrine doesn't pretend otherwise. Anyone treating it as a budget CVT-20 is making a mistake procurement never intended to allow.
Same modular panel logic and parts-commonality philosophy as the LUT-10, scaled down rather than simplified. A mechanic who knows the LUT-10 should be able to service a TUC-5 without relearning the platform.
Game Data // Tactical Unit Record
Tabletop movement values remain undefined in the current technical source.
Field Procurement Archive