The Setup
74 vessel loitering events in the last 45 days were classified as slow_roll events near ship-to-ship transfer hotspots. The vessels involved were moving at 0.20–0.25 knots — too slow to be in transit, too purposeful to be adrift — within detection radius of known STS transfer zones.
When a vessel executes a slow-roll near an STS hotspot, one question arises for every supply chain operation downstream: did cargo change hands? If it did, the port call record may not reflect it. And if the port call record doesn't reflect it, every commercial real estate operator priced off declared port throughput is working with incomplete data.
Houston port-adjacent cells average a development pipeline score of 4 out of 100. That floor has held across three consecutive scoring cycles.
The Chain
74 events is a small number relative to the 2,894 total loitering detections in the same 45-day window. But it's the specific subset that overlaps with transfer zone proximity and slow-speed movement — the two conditions that characterize pre-transfer positioning before an undeclared exchange.
Ship-to-ship transfers that occur outside declared berth visits don't generate port call records. The cargo that moves in those transactions doesn't appear in throughput data until the receiving vessel declares at its next port. In corridors with high STS activity — Houston Ship Channel, the approaches to Singapore, Rotterdam outer roads — the gap between declared throughput and actual cargo movement can be material.
Bonded warehouse operators and 3PL facilities price inventory-holding decisions on declared port traffic. If 74 vessel positioning events in a 45-day window generated STS transfers that bypassed that declared data, the operators holding cargo buffer positions near those corridors didn't know. The cargo signal they received was incomplete by design.
Houston port-adjacent average development pipeline score: 4.0 across 130 scored cells as of May 26, 2026. The pipeline score aggregates permit velocity, construction activity, and development momentum. A score of 4 is the tracked floor — not a single Houston cell scores above 10 on pipeline in the current window.
The Implication
A pipeline score of 4 in a high-throughput port corridor like Houston is not a lack-of-demand story. 71 vessels are currently waiting at Houston with a median wait of 9 hours, cycling through tracked berths. Demand for logistics-adjacent space exists in the observable record.
The gap between declared vessel activity (measurable, used for pricing) and slow-roll hotspot proximity events (indicative of undeclared activity, not used for pricing) describes an opacity premium that port-adjacent CRE operators are implicitly carrying. Development doesn't follow cargo you can't confirm.
Bonded storage demand may actually increase when cargo opacity increases. Commodity traders need buffer positions precisely because they cannot confirm routing on the first pass. The pipeline score does not capture leased-and-occupied space — only active development. A market with high latent demand and suppressed new construction may be operating at full utilization without triggering a pipeline signal. That distinction matters when interpreting the 4.0 floor.
This pattern isn't unique to Houston. Rotterdam's STS activity generates the same declared-versus-actual gap. Singapore's outer roads do. What Houston provides is a numeric floor to benchmark against: pipeline = 4, across all 130 port-adjacent cells, for three consecutive cycles.
What to Watch
Slow_roll/hotspot_vicinity event velocity is the upstream signal. Currently 74 events in 45 days. An increase to 100 or more in the next window would widen the implied gap between declared and undeclared cargo movement.
Hydrostatic draft coverage is the data integrity signal. 47% of vessel visits currently arrive without usable draft data (as of the May 1 coverage gap analysis). Slow-roll events near hotspots contribute to this gap — vessels that transfer cargo at sea may arrive at port at a different draft than predicted from their last declared position.
Houston pipeline score progression: three consecutive cycles at floor. A break above 4 — even one cell — would be the first measurable development signal in this geography since tracking began, and would reprice the constraint assumption.
Limitations
The 74 slow_roll/hotspot events are not confirmed STS transfers. They represent vessels with the positioning signature of pre-transfer behavior. The risk model assigns medium or high classification; it does not adjudicate intent or confirm cargo exchange.
Pipeline scores in this analysis aggregate the entire Houston metro rather than port-adjacent cells exclusively. Port-adjacent cells are a geographic subset that may diverge from the metro average. A cell-level breakdown limited to port-adjacent geography would require a spatial join not reflected in the metro-level numbers cited here.
The connection between loitering event frequency and pipeline score suppression is observational. Multiple independent factors — land costs, zoning constraints, capital market conditions — also affect pipeline scores and may be the primary drivers.
Data as of May 22–26, 2026. Sources: Axiom Overwatch loitering_events (74 slow_roll/hotspot_vicinity events, April 11 – May 22); Axiom Locus cell_scores (Houston metro, 130 cells, scored May 26, 2026).