Triumph IV
Pilot vessel · United States · built 2004 · AIS Class B
In short
Triumph IV (Pilot vessel, United States flag) was last seen on AIS on , under way at 15.6 kn, near Vancouver (North Pacific Ocean). Its last detected port call was at Mersin: arrived Nov 2, 2026, left Nov 4, 2026. Managing owner (USCG): ANCHORAGE LAUNCH SERVICES LLC (source: US Coast Guard — Merchant Vessels of the United States (documented vessels)).
- Vessel type
- Pilot vessel
- Flag
- United States
- Year built
- 2004
- Gross tonnage
- —
- Size (length × beam)
- 13 m × 5 m
- Managing owner (USCG)
- ANCHORAGE LAUNCH SERVICES LLC

Last reported position: 45.6433° N, 122.7364° W · North Pacific Ocean · See on the map
Watch this ship
Get an email when Triumph IV arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 18, 2026, 17:36 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Triumph IV reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans
Get alerts on your phone: Voydar for iPhone
Last reported position
received- Position
- 45.6433° N, 122.7364° W
- Area
- North Pacific Ocean
- Status
- UndefinedWhat do AIS statuses mean?
- Speed
- 15.6 kn
- Course
- 96°
- Heading
- —
- Compass: course over ground 96°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 1 port call (Mersin).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Triumph IV's track before the last 30 days. Voydar has recorded its port calls since August 18, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 13 mone tick every 2 m
Beam 5 mPlan outline, to scale
- Name
- Triumph IV
- IMO numberWhat is an IMO number?
- 9311555
- MMSIWhat is an MMSI?
- 367177660
- Call signWhat is a call sign?
- WBE7851
- Flag
- United States
- Vessel type
- Pilot vessel
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- 13 m
- Beam
- 5 m
- Year built
- 2004
A tag next to a value names the register that supplied it (hover or tap it for the record and date). Values without a tag come from the ship's own AIS broadcasts or from Wikidata. Position and identity are derived live from AIS.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
- Managing owner (USCG)
- ANCHORAGE LAUNCH SERVICES LLC(not linked to a company record)Source: US Coast Guard — Merchant Vessels of the United States (documented vessels) · reported · high confidence · retrieved Oct 6, 2026Coast Guard documentation record (2026-09 file) matched to this ship by call sign and vessel name. The managing owner is the company the Coast Guard has on record for the ship's certificate of documentation.
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · high confidence · retrieved Nov 16, 2026
- Ship radio licensee (FCC)
- Anchorage Launch Service Co.(not linked to a company record)Source: FCC Universal Licensing System — ship station licences · since 2017 · reported · high confidence · retrieved Nov 17, 2026Licence matched to this ship by MMSI and call sign. The licensee holds the radio licence; it is not necessarily the owner.
Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →
Timeline
Dated events for this ship from every source Voydar holds, newest first. Each line names its source; derived items say how they were derived.
Owner, operator and manager changes found by comparing yearly EU MRV reports are dated to the reporting year ("during 2025"), not to a day. Port calls here are the most recent only; the full lists are further down.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2025 | 1,416 t | 442 t | 101 days | 74 kg |
Technical efficiency: EEXI (14.03 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
Compared with ships of its type
Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “General cargo ship”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile22.14 g per tonne-nautical mile
- Lowest reportedHighest reported
21% of the 661 ships in this group reported a lower figure.
Group: lower quartile 23.23 · median 30.36 · upper quartile 42.59
- CO₂ per nautical mile sailed73.8 kg per nautical mile
- Lowest reportedHighest reported
24% of the 2,956 ships in this group reported a lower figure.
Group: lower quartile 74.8 · median 110.6 · upper quartile 185.8
Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated
Port calls
Two kinds of evidence, kept apart: calls Voydar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.
Detected from AIS AIS-detected
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Mersin TRMER | Nov 2, 2026, 11:49 UTC | Nov 4, 2026, 03:28 UTC | 39 h 39 min |
| Haifa ILHFA | Aug 18, 2026, 07:11 UTC | Aug 24, 2026, 07:43 UTC | 6 d 0 h |
Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.
Behaviour at sea Voydar-derived
Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.
| When | What we observed | Confidence |
|---|---|---|
| Nov 8, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,011 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 5, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,424 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 4, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,599 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 3, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,597 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 2, 2026, 22:26 UTC | Draught change Reported draught went from 6.7 m to 4.6 m while in port at Mersin. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Nov 2, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,597 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 1, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,605 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 31, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,607 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 30, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,607 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 28, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,607 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 27, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,607 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 26, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,607 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 25, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,605 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 23, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,607 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 22, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,607 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 21, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,607 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 20, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,601 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 19, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,607 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 18, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,605 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 17, 2026, 00:00 UTC | IMO used twice IMO 9311555 was broadcast by two ships (MMSI 325143900 and 367177660) 10,607 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.
Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.
Frequently asked questions
- What kind of ship is Triumph IV?
- Triumph IV is a pilot vessel sailing under the flag of United States, built in 2004. The vessel is 13 m long with a beam of 5 m.
- Who is recorded as the owner or manager of Triumph IV?
- ANCHORAGE LAUNCH SERVICES LLC is recorded as Managing owner (USCG) for Triumph IV (source: US Coast Guard — Merchant Vessels of the United States (documented vessels)). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for Triumph IV?
- Voydar has no matched sanctions record displayed for Triumph IV from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels, the New Zealand Russia Sanctions Register and the French national asset-freeze register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Triumph IV. Missing records do not establish whether the ship has been detained.
Full Vessel Report
A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.
Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.
Every fact on this page stays free.
Know this ship?
Help other readers. Member posts are shown as member content, never as sourced data.
- Date, place and an optional note
- Members who know her can answer
- Suggest a correctionChecked against sources before anything changes
Use this data
This page is also available as JSON, free, with the source and licence of every section. Sections whose sources do not permit redistribution are listed as withheld.
GET /api/v1/vessels/9311555Cite this page
Triumph IV. Voydar (voydar.com). https://www.voydar.com/vessel/9311555-triumph-iv. Retrieved November 18, 2026.
Each fact above names its own source and date. Cite that primary source too when you rely on a fact.
Using this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.