
One vessel, every compliance signal in one place: sanctions exposure path, composite risk, dark-fleet behaviour, flag history and safety record.
No sanctions exposure was found, but the composite risk read is elevated. See the breakdown below.
Sanctions exposure screens the hull and its ownership chain against official OFAC, EU, UN and UK designations, then propagates a sanctioned owner or parent down to the vessels it controls. The composite risk read blends age, flag register, port-state detentions, dark-fleet behaviour and sanctions exposure, weighted by how much evidence is present. Every signal shows its own evidence. This is decision support for a compliance review, not a legal determination.
Composite Risk
Multiple adverse factors, or a hard ship-specific signal, lift this hull above the fleet norm.
A coverage-weighted blend of the 2 components we could read for this hull — the weights renormalise over only the components present, so a thin read is never inflated and a hull is never credited a “safe 0” for a signal it has no row for. This headline is flagged low-confidence (a thin or structural-only read) and should not be treated as a verdict. Higher means riskier. Derived in-house from government-open port-State-control, flag, sanctions and our own vessel data; weight it by the coverage above.
Compliance
On 24 June 2026, the cargo vessel "MOUNT SEYMOUR", while under the conduct of a pilot, reported having struck the wharf while berthing in the Second Narrows of Vancouver, BC. The vessel was secured and the crew reported no apparent damage to the hull.
On 23 February 2025, the cargo ship "MOUNT SEYMOUR", with 18 people onboard, reported a crew member being injured during testing of a submersible pump while the vessel was alongside at the Lynnterm no.1 berth in Vancouver, BC. The injured crew member was treated by paramedics before being taken to the hospital. He was released from the hospital later the same day.
On 27 March 2022, the bulk carrier "MOUNT SEYMOUR", while under the conduct of a pilot, reported that one of its main engines had failed soon after departure from Squamish, BC. The vessel returned and anchored at a Squamish emergency anchorage by using its other engine while the crew members carried out repairs.
Recorded marine occurrences naming this vessel.