Skip to content

SAMOS

Oil tanker · Bahamas · AIS Class A

IMO9486934MMSI311040100Call signC6YO4Last AIS position Oct 2, 2026, 23:09 UTC

In short

SAMOS (Oil tanker, Bahamas flag) was last seen on AIS on , not moving, near Benicia (North Pacific Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is US LGB > US SFO; its reported draught is 11 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 20:34 UTC).

Current voyage: from Oakland (departed Sep 25, 2026, 18:52 UTC) to US LGB > US SFO

Vessel type
Oil tanker
Year built
—
Gross tonnage
—
Size (length × beam)
—
Registered owner
—

Watch this ship

Get an email when SAMOS 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 SAMOS.

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.

Last reported position

received
Position
38.0329° N, 122.1295° W
Area
North Pacific Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0 kn
Course
77°
Heading
238°
38.0329° N, 122.1295° W
Open the full live map →

Last 30 days: 1 port call (Oakland).

Port calls are detected by Voydar 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
SAMOS
IMO numberWhat is an IMO number?
9486934
MMSIWhat is an MMSI?
311040100
Call signWhat is a call sign?
C6YO4
AIS ship type
Tanker
Length overall
—
Beam
—
Year built
—

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
Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 2026

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.

DateEventSource
Left OaklandAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at OaklandAIS-detectedVoydar port-call detector (AIS geofence)
ISM manager: JHI Steamship Co (previously SAMOS STEAMSHIP CO.)Voydar relationship-change derivation (derived by Voydar from EU MRV (THETIS-MRV) emissions)
Reported departure from Long BeachAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at Long BeachAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from CARQUINEZ STRAIT, CAAuthority-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
20182,304 t738 t32 days449 kg
20191,185 t380 t8 days504 kg
20203,187 t1,010 t26 days477 kg
20213,751 t1,199 t31 days494 kg
20225,785 t1,834 t48 days418 kg
20237,365 t2,344 t56 days491 kg
20241,207 t382 t8 days560 kg
20254,526 t1,428 t44 days394 kg

Technical efficiency: EIV (3.81 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 Voydar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Oakland USOAKSep 24, 2026, 17:02 UTCSep 25, 2026, 18:52 UTC25 h 50 min

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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Long Beach USLGBDepartureJun 19, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBArrivalJun 7, 2015(date only)—USACE foreign traffic vessel entrances & clearances
CARQUINEZ STRAIT, CADepartureMay 6, 2015(date only)—USACE foreign traffic vessel entrances & clearances
CARQUINEZ STRAIT, CAArrivalApr 21, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBDepartureApr 17, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBArrivalMar 28, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBDepartureMar 24, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBArrivalMar 24, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBDepartureFeb 27, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBArrivalFeb 24, 2015(date only)—USACE foreign traffic vessel entrances & clearances
SAN PABLO BAY AND MARE ISLAND STRAIT, CADepartureFeb 20, 2015(date only)—USACE foreign traffic vessel entrances & clearances
SAN PABLO BAY AND MARE ISLAND STRAIT, CAArrivalFeb 19, 2015(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: February 10, 2015.

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.

WhenWhat we observedConfidence
Sep 27, 2026, 08:07 UTC
Alongside another ship

Stayed within 49 m of HORTEN at low speed for 2 h 10 min, 140 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed.

HORTEN →

Method seadar.behaviour.sts_candidate v1

Medium (65%)

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.

How these are computed →

Frequently asked questions

Where is SAMOS now?
SAMOS (Oil tanker, Bahamas flag) was last seen on AIS on Oct 2, 2026, 23:09 UTC, not moving, near Benicia (North Pacific Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was US LGB > US SFO (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 20:34 UTC). This report does not confirm the ship’s current route.
What kind of ship is SAMOS?
SAMOS is an oil tanker sailing under the flag of Bahamas.
What sanctions and inspection records does Voydar hold for SAMOS?
Voydar has no matched sanctions record displayed for SAMOS 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 SAMOS. 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/9486934
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