MANASLU appears on the OFAC SDN list, the Canadian autonomous sanctions list, the EU list of designated vessels and the UK Sanctions List under the IRAN-EO13902, Russia, and Russia (Reg. 833/2014 Annex XLII) programs. Verify at OFAC.
Every vessel on:OFAC SDN listCanadian autonomous sanctions listEU list of designated vesselsUK Sanctions List
MANASLU
Oil tanker · Cameroon · built 2008 · AIS Class A
In short
MANASLU (Oil tanker, Cameroon flag) was last seen on AIS on , under way at 11.1 kn, in the Mediterranean Sea. 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 GE BUS; its reported draught is 7 m (voyage report via AISstream.io global terrestrial AIS, received Nov 3, 2026, 22:44 UTC). It appears on 4 sanctions lists (details below).
Current voyage: from Kumport (departed Oct 16, 2026, 09:10 UTC) to GE BUS
- Vessel type
- Oil tanker
- Flag
- Cameroon
- Year built
- 2008
- Gross tonnage
- 29,605
- Size (length × beam)
- 183 m
- Registered owner
- —
Last reported position: 38.2894° N, 25.4604° E · Mediterranean Sea · See on the map
Watch this ship
MANASLU has not been received for a while. Follow it for an email update when Voydar receives a new position, and for arrival and departure alerts.
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 17, 2026, 17:19 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for MANASLU 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
- 38.2894° N, 25.4604° E
- Area
- Mediterranean Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 11.1 kn
- Course
- 343°
- Heading
- 344°
- Compass: course over ground 343°, heading 344°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Voydar detected no port call in the last 30 days.
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows MANASLU's track before the last 30 days. Voydar has recorded its port calls since July 29, 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 183 mone tick every 25 m
- Name
- MANASLU
- IMO numberWhat is an IMO number?
- 9388027
- MMSIWhat is an MMSI?
- 613442789
- Call signWhat is a call sign?
- TJM80L
- Flag
- Cameroon
- Gross tonnageGross tonnage vs deadweight
- 29,605
- Length overall
- 183 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 3, 2026.32 m
- Year built
- 2008
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.
AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via AISstream.io global terrestrial AIS on November 3, 2026.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
- Owner or operator (sanctions listing)
- Zulu Ships Management(not linked to a company record)Source: UK Sanctions List (FCDO) · reported · medium confidence · retrieved Nov 17, 2026
- Builder
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026
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.
| Date | Event | Source |
|---|---|---|
| Left KumportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KumportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left KumportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KumportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Listed on the Canadian autonomous sanctions list (Russia) | Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA) | |
| Listed on the UK Sanctions List (Russia) | UK Sanctions List (FCDO) | |
| Listed on the EU designated vessels (Official Journal) (Russia (Reg. 833/2014 Annex XLII)) | EU designated vessels (Reg. 833/2014 Annex XLII; Reg. 2017/1509 Annex XIV) | |
| Reported departure from Texas CityAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at Texas CityAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from BeaumontAuthority-reported | USACE 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.
Sanctions listings
Every listing of this ship on the sanctions lists Voydar tracks, current and past.
| List | Programme | Listed as | Listed | Status |
|---|---|---|---|---|
| Canadian autonomous sanctions list | Russia | Manaslu | Mar 25, 2026 | In force |
| UK Sanctions List | Russia | MANASLU | Feb 24, 2026 | In force |
| EU designated vessels (Official Journal) | Russia (Reg. 833/2014 Annex XLII) | Manaslu | Oct 24, 2025 | In force |
| OFAC SDN list (US) | IRAN-EO13902 | MANASLU | not published by the list | In force |
Source: Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA). Contains information licensed under the Open Government Licence – Canada. Licence: Open Government Licence – Canada.
Source: UK Sanctions List (FCDO). Contains public sector information licensed under the Open Government Licence v3.0. Licence: OGL v3.
Source: Council Regulation (EU) No 833/2014, Annex XLII, and Council Regulation (EU) 2017/1509, Annex XIV (Official Journal of the European Union); list compiled by the Danish Maritime Authority. Licence: EU legislation (Official Journal): reuse "for commercial or non-commercial purposes" (Decision 2011/833/EU); facts.
Source: OFAC Specially Designated Nationals list. Licence: US Government public domain (17 U.S.C. §105).
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 |
|---|---|---|---|---|
| 2018 | 4,341 t | 1,380 t | 56 days | 368 kg |
| 2019 | 2,577 t | 810 t | 35 days | 283 kg |
| 2020 | 12,354 t | 3,924 t | 124 days | 343 kg |
| 2023 | 3,638 t | 1,149 t | 58 days | 289 kg |
Technical efficiency: EEXI (5.13 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 2023 sits among the ships EU MRV lists as “Oil tanker”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile16.89 g per tonne-nautical mile
- Lowest reportedHighest reported
81% of the 1,824 ships in this group reported a lower figure.
Group: lower quartile 6.09 · median 8.46 · upper quartile 13.3
- CO₂ per nautical mile sailed288.9 kg per nautical mile
- Lowest reportedHighest reported
18% of the 1,922 ships in this group reported a lower figure.
Group: lower quartile 320 · median 405.4 · upper quartile 490.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 |
|---|---|---|---|
| Kumport TRKMX | Oct 15, 2026, 12:05 UTC | Oct 16, 2026, 09:10 UTC | 21 h 5 min |
| Kumport TRKMX | Jul 29, 2026, 03:50 UTC | Jul 31, 2026, 08:13 UTC | 2 d 4 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Texas City USTXT | Departure | Dec 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Texas City USTXT | Arrival | Dec 13, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Departure | Dec 11, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Arrival | Dec 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Departure | Dec 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Arrival | Dec 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baton Rouge USBTR | Departure | Oct 21, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baton Rouge USBTR | Arrival | Oct 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Ponce PRPSE | Departure | Oct 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Jul 11, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Jul 11, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Arrival | Feb 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: January 21, 2009.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- What kind of ship is MANASLU?
- MANASLU is an oil tanker sailing under the flag of Cameroon, built in 2008 by Sungdong Shipbuilding & Marine Engineering. The vessel is 183 m long and has a gross tonnage of 29,605.
- What sanctions and inspection records does Voydar hold for MANASLU?
- MANASLU appears on the OFAC SDN list, the Canadian autonomous sanctions list, the EU list of designated vessels and the UK Sanctions List under the IRAN-EO13902, Russia, and Russia (Reg. 833/2014 Annex XLII) programs. No matched inspection records are displayed for MANASLU. 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/9388027Cite this page
MANASLU. Voydar (voydar.com). https://www.voydar.com/vessel/9388027-manaslu. Retrieved November 17, 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.