Skip to content

Seattle Slew

Bulk carrier · Panama · built 2010 · AIS Class A

IMO9573737MMSI351079000Call sign3FMN9Last AIS position Sep 27, 2026, 12:25 UTC

In short

Seattle Slew (Bulk carrier, Panama flag) was last seen on AIS on , under way at 11.3 kn, in the East China Sea. Seadar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is TW KHH (Kaohsiung); its reported draught is 9.1 m (voyage report via AISstream.io global terrestrial AIS, received Sep 27, 2026, 11:29 UTC). ISM manager: Golden Union Shipping Co SA (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Vessel type
Bulk carrier
Flag
Panama
Year built
2010
Gross tonnage
92,758
Size (length × beam)
292 m

Watch this ship

Get an email when Seattle Slew arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

We email you a link and a code. That creates a free account, no password or card, and follows Seattle Slew.

Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.

By continuing you accept the Terms and the Privacy policy.

Photo of SEATTLE SLEW
Photo: Alf van Beem · Licence: CC0 · via Wikimedia Commons

Last reported position

received
Position
24.2957° N, 120.1709° E
Area
East China Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
11.3 kn
Course
213°
Heading
214°
24.2957° N, 120.1709° E
Open the full live map →

Seadar detected no port call in the last 30 days.

Port calls are detected by Seadar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)

Try the live demo, no sign-up

Identity & particulars

Name
Seattle Slew
IMO numberWhat is an IMO number?
9573737
MMSIWhat is an MMSI?
351079000
Call signWhat is a call sign?
3FMN9
Flag
Panama
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
92,758
Length overall
292 m
Beam
—
Year built
2010

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.

ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Sep 28, 2026
Builder
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026

Timeline

Dated events for this ship from every source Seadar holds, newest first. Each line names its source; derived items say how they were derived.

DateEventSource
Reported departure from BaltimoreAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at BaltimoreAuthority-reportedUSACE foreign traffic vessel entrances & clearances

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.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20223,268 t1,047 t33 days409 kg
20241,185 t380 t12 days473 kg
20253,112 t989 t31 days515 kg

Technical efficiency: EEXI (2.37 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.

Port calls

Two kinds of evidence, kept apart: calls Seadar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Baltimore USBALDepartureMay 20, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALArrivalMay 18, 2012(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: May 18, 2012.

Frequently asked questions

Where is Seattle Slew now?
Seattle Slew (Bulk carrier, Panama flag) was last seen on AIS on Sep 27, 2026, 12:25 UTC, under way at 11.3 kn, in the East China Sea. Seadar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was TW KHH (voyage report via AISstream.io global terrestrial AIS, received Sep 27, 2026, 11:29 UTC). This report does not confirm the ship’s current route.
What kind of ship is Seattle Slew?
Seattle Slew is a bulk carrier sailing under the flag of Panama, built in 2010 by Imabari Shipbuilding Hiroshima Shipyard. The vessel is 292 m long and has a gross tonnage of 92,758.
Who is recorded as the owner or manager of Seattle Slew?
Golden Union Shipping Co SA is recorded as ISM manager for Seattle Slew (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Seadar hold for Seattle Slew?
Seadar has no matched sanctions record displayed for Seattle Slew from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Seattle Slew. Missing records do not establish whether the ship has been detained.

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/9573737
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using this data in code?

Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro adds internal business use; API plans add building the data into your own products.

See plans