Skip to main content
ISWAN SeafarerHelp +44 800 012 1004 · free, 24/7, multilingualmore ▾
Skip to content
Seafarer Index

Seacor Resolve

IMO 9232735 · MMSI 338721000

Before joining this vessel — checklist

Work through each item before signing your SEA or travelling to the vessel.

Not enough public data — flag state, owner and manager are all unknown for this vessel. Verify details directly with the employer before proceeding.
  1. 1. Verify vessel identity

    Confirm the vessel name and IMO number match. Seacor Resolve (IMO 9232735)

  2. 2. Check the flag state record

    Flag unknown — ask the employer. How to read flag risk · Paris/Tokyo MoU lists

  3. 3. Check the company

    Owner unknown. Owner and manager unknown — ask the employer.

  4. 4. Review your contract (SEA)

    Read your Seafarer Employment Agreement before joining. SEA rights guide · Contract reading checklist

  5. 5. Check repatriation terms

    Confirm repatriation is covered and the conditions are clear. Repatriation rights guide

  6. 6. Watch for recruitment-fee red flags

    You should never pay to get a job at sea. Recruitment fees & scams guide

  7. 7. Save emergency contacts

    Record ITF, flag-state authority, and welfare helpline numbers before departure. Emergency contact planner

Data sources and methodology: /sources

Not enough public data — owner, manager and flag are all unknown for this vessel.
Type
anchor handling tug supply vessel
Flag
—
Year built
2000
Builder
North American Shipbuilding
GT
—
DWT
—
LOA
—
Beam
—
Draft
—
Class
—
Owner
—
Manager
—

Indexed from Wikidata (Q117103555).

Overview

Seacor Resolve is a anchor handling tug supply vessel built in 2000 by North American Shipbuilding.

Overview synthesized from public-registry fields. Confirm on board — the certificates posted on the bridge and in the SMS are the authoritative live documents.

PSC detention history

No detentions in the last 2 years.

High confidence

Editorial confidence: how we grade. Data sources and methodology: /sources.

Found an error on this page? Report it →