Skip to content

Almi Odyssey

Oil tanker · Liberia · built 2013 · AIS Class A

IMO9579559MMSI636015880Call signD5DH4Last AIS position Oct 1, 2026, 19:52 UTC

In short

Almi Odyssey (Oil tanker, Liberia flag) was last seen on AIS on , not moving, in the North Pacific Ocean. Its crew-entered AIS destination is US PAL (Port Allen); its reported draught is 9.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 19:15 UTC). ISM manager: ALMI TANKERS SA (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Oil tanker
Year built
2013
Gross tonnage
84,216
Size (length × beam)
—
ISM manager
ALMI TANKERS SA

Watch this ship

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

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 ALMI ODYSSEY
Photo: Alf van Beem · Licence: Public domain · via Wikimedia Commons

Last reported position

received
Position
33.149° N, 118.0108° W
Area
North Pacific Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0.4 kn
Course
78°
Heading
25°
33.149° N, 118.0108° W
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
Almi Odyssey
IMO numberWhat is an IMO number?
9579559
MMSIWhat is an MMSI?
636015880
Call signWhat is a call sign?
D5DH4
AIS ship type
Tanker
Gross tonnageGross tonnage vs deadweight
84,216
Length overall
—
Beam
—
Year built
2013

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 years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 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 Corpus ChristiAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at Corpus ChristiAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-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
20180 t0 t0 days—
20190 t0 t0 days—
20200 t0 t0 days—
202118,828 t5,968 t98 days679 kg
20225,024 t1,611 t32 days550 kg
20239,195 t2,916 t99 days447 kg
20245,024 t1,609 t45 days531 kg
20254,083 t1,302 t40 days391 kg

Technical efficiency: EEDI (2.83 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
Corpus Christi USCRPDepartureDec 18, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPArrivalDec 17, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureNov 8, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalNov 8, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureOct 29, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalOct 28, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Port Arthur USPOADepartureAug 3, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Port Arthur USPOAArrivalAug 2, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureJul 2, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPArrivalJul 2, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureAug 24, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPArrivalAug 15, 2015(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: November 25, 2013.

Behaviour at sea Seadar-derived

Patterns Seadar 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 23, 2026, 04:26 UTC
Loitering

Stayed within 10 km for 16 h 44 min (drifting), 47 km from the nearest port and outside known anchorages.

Method seadar.behaviour.loitering v1

Medium (60%)
Sep 22, 2026, 06:05 UTC
Loitering

Stayed within 10 km for 13 h 52 min (drifting), 41 km from the nearest port and outside known anchorages.

Method seadar.behaviour.loitering v1

Medium (60%)

Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.

Derived from AIS positions of feeds whose terms allow display on Seadar. 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 Almi Odyssey now?
Almi Odyssey (Oil tanker, Liberia flag) was last seen on AIS on Oct 1, 2026, 19:52 UTC, not moving, in the North Pacific Ocean. The crew-entered destination was US PAL (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 19:15 UTC). This report does not confirm the ship’s current route.
What kind of ship is Almi Odyssey?
Almi Odyssey is an oil tanker sailing under the flag of Liberia, built in 2013. The vessel has a gross tonnage of 84,216.
Who is recorded as the owner or manager of Almi Odyssey?
ALMI TANKERS SA is recorded as ISM manager for Almi Odyssey (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Seadar hold for Almi Odyssey?
Seadar has no matched sanctions record displayed for Almi Odyssey 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 Almi Odyssey. 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/9579559
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