MANA KAI
Sailing vessel · Malta · built 2008 · AIS Class B
In short
MANA KAI (Sailing vessel, Malta flag) was last seen on AIS on , under way at 6.5 kn, in the North Atlantic Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its last detected port call was at Barcelona: arrived Nov 8, 2026, left Nov 13, 2026. ISM manager: BESIKTAS LIKID TASIMACILIK DENIZCILIK TICARET A.S. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Sailing vessel
- Flag
- Malta
- Year built
- 2008
- Gross tonnage
- 30,123
- Size (length × beam)
- 183 m × 32 m

Last reported position: 34.1848° N, 8.4467° W · North Atlantic Ocean · See on the map
Watch this ship
MANA KAI 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, 23:50 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for MANA KAI 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
- 34.1848° N, 8.4467° W
- Area
- North Atlantic Ocean
- Status
- UndefinedWhat do AIS statuses mean?
- Speed
- 6.5 kn
- Course
- 233°
- Heading
- —
- Compass: course over ground 233°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 2 port calls (Barcelona and Vasilikos).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows MANA KAI's track before the last 30 days. Voydar has recorded its port calls since June 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 183 mone tick every 25 m
Beam 32 mPlan outline, to scale
- Name
- MANA KAI
- IMO numberWhat is an IMO number?
- 9396787
- MMSIWhat is an MMSI?
- 249263000
- Call signWhat is a call sign?
- 9HC274
- Flag
- Malta
- Vessel type
- Sailing vessel
- Gross tonnageGross tonnage vs deadweight
- 30,123
- Length overall
- 183 m
- Beam
- 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.
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 · high confidence · retrieved Nov 16, 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 BarcelonaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BarcelonaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left VasilikosAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at VasilikosAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Call sign changed from 3E5429 to 3E4790 | AIS, seen by Voydar | |
| Port State Control inspection at New Orleans, Louisiana | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Inspection at New Orleans, Louisiana | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Mobile, Alabama | USCG PSIX / CGMIX inspections | |
| Inspection at Mobile, Alabama | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Houston, Texas | USCG PSIX / CGMIX inspections | |
| Reported departure from PORT OF SOUTH LOUISIANA (LA)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at GalvestonAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from GalvestonAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Inspection at NEW HAVEN, Connecticut | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Port Jefferson Station, New York | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at PHILADELPHIA, Pennsylvania | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Port Arthur, Texas | USCG PSIX / CGMIX inspections |
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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Nov 21, 2019 | Vessel InspectionPSC | New Orleans, Louisiana | clean |
| Feb 19, 2019 | Vessel InspectionPSC | San Pedro, California | clean |
| Jan 18, 2019 | Vessel Inspection | New Orleans, Louisiana | clean |
| Dec 13, 2018 | Vessel InspectionPSC | Mobile, Alabama | clean |
| Dec 9, 2018 | Vessel Inspection | Mobile, Alabama | clean |
| Oct 12, 2017 | Vessel InspectionPSC | Houston, Texas | clean |
| Sep 15, 2016 | Vessel Operational Control | NEW HAVEN, Connecticut | clean |
| Sep 14, 2016 | Vessel InspectionPSC | Port Jefferson Station, New York | clean |
| Jun 18, 2015 | Vessel InspectionPSC | PHILADELPHIA, Pennsylvania | clean |
| Apr 30, 2014 | Vessel InspectionPSC | Port Arthur, Texas | clean |
| Apr 27, 2014 | Vessel Inspection | Houston, Texas | clean |
| Feb 17, 2014 | Vessel Inspection | New Orleans, Louisiana | clean |
| Oct 25, 2013 | Vessel InspectionPSC | New Orleans, Louisiana | clean |
| Oct 24, 2013 | Boarding | New Orleans, Louisiana | clean |
| Jun 19, 2013 | Vessel Inspection | Miami Beach, Florida | clean |
| May 23, 2013 | Vessel Inspection | Lake Charles, Louisiana | clean |
| Apr 22, 2013 | Vessel InspectionPSC | Lake Charles, Louisiana | clean |
| Aug 23, 2011 | Vessel InspectionPSC | Christiansted, Virgin Islands | clean |
| Aug 17, 2011 | Boarding | San Juan, Puerto Rico | clean |
| Oct 28, 2010 | Incident Investigation | WASHINGTON, District of Columbia | clean |
Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.
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 | 11,093 t | 3,530 t | 174 days | 380 kg |
| 2019 | 1,899 t | 608 t | 25 days | 318 kg |
| 2020 | 9,823 t | 3,098 t | 73 days | 501 kg |
| 2023 | 2,647 t | 836 t | 33 days | 329 kg |
| 2024 | 4,375 t | 1,381 t | 84 days | 341 kg |
| 2025 | 3,803 t | 1,200 t | 76 days | 329 kg |
Technical efficiency: EIV (6.88 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 “Chemical tanker”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile18.16 g per tonne-nautical mile
- Lowest reportedHighest reported
60% of the 1,489 ships in this group reported a lower figure.
Group: lower quartile 10.24 · median 15.04 · upper quartile 25.97
- CO₂ per nautical mile sailed328.5 kg per nautical mile
- Lowest reportedHighest reported
85% of the 1,516 ships in this group reported a lower figure.
Group: lower quartile 203.4 · median 250.2 · upper quartile 301
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 |
|---|---|---|---|
| Barcelona ESBCN | Nov 8, 2026, 12:06 UTC | Nov 13, 2026, 12:34 UTC | 5 d 0 h |
| Vasilikos CYVAS | Oct 23, 2026, 12:17 UTC | Oct 27, 2026, 11:33 UTC | 3 d 23 h |
| IJmuiden/Velsen NLIJM | Oct 3, 2026, 09:49 UTC | Oct 3, 2026, 10:58 UTC | 1 h 8 min |
| Amsterdam NLAMS | Oct 1, 2026, 23:08 UTC | Oct 3, 2026, 08:53 UTC | 33 h 45 min |
| Amsterdam NLAMS | Sep 22, 2026, 17:51 UTC | Sep 23, 2026, 17:05 UTC | 23 h 14 min |
| IJmuiden/Velsen NLIJM | Sep 22, 2026, 16:03 UTC | Sep 22, 2026, 16:50 UTC | 47 min |
| Tauranga NZTRG | Sep 20, 2026, 07:33 UTC | Sep 22, 2026, 12:20 UTC | 2 d 4 h |
| Hoek van Holland NLHVH | Sep 15, 2026, 05:35 UTC | Sep 17, 2026, 00:07 UTC | 42 h 32 min |
| Zandvliet BEZVT | Jun 19, 2026, 18:40 UTC | Jun 19, 2026, 20:16 UTC | 1 h 36 min |
| Tauranga NZTRG | Jun 18, 2026, 18:23 UTC | Jun 21, 2026, 02:00 UTC | 2 d 7 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 |
|---|---|---|---|---|
| PORT OF SOUTH LOUISIANA (LA) | Departure | Oct 2, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Galveston USGLS | Arrival | Sep 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Galveston USGLS | Departure | Sep 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| NORTHVILLE, L.I., NY | Departure | Sep 16, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| NORTHVILLE, L.I., NY | Arrival | Sep 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Mar 21, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Mar 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Jul 8, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Jul 6, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PAULSBORO, NJ | Departure | Jun 18, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PAULSBORO, NJ | Arrival | Jun 17, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Brownsville USBRO | Departure | Jun 11, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: June 12, 2009.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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 15, 2026, 00:00 UTC | IMO used twice IMO 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 1,276 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 13, 2026, 12:17 UTC | Draught change Reported draught went from 7.6 m to 10.1 m while in port at Barcelona. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Nov 13, 2026, 00:00 UTC | IMO used twice IMO 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 398 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 12, 2026, 00:00 UTC | IMO used twice IMO 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 295 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 11, 2026, 00:00 UTC | IMO used twice IMO 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 115 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 10, 2026, 00:00 UTC | IMO used twice IMO 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 311 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 9, 2026, 00:00 UTC | IMO used twice IMO 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 367 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 8, 2026, 00:00 UTC | IMO used twice IMO 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 368 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 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 2,493 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 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 2,537 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 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 2,537 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 24, 2026, 00:00 UTC | IMO used twice IMO 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 2,537 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 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 2,539 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 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 2,205 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 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 1,642 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 16, 2026, 00:00 UTC | IMO used twice IMO 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 723 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 8, 2026, 00:00 UTC | IMO used twice IMO 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 1,205 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 7, 2026, 00:00 UTC | IMO used twice IMO 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 1,480 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 4, 2026, 00:00 UTC | IMO used twice IMO 9396787 was broadcast by two ships (MMSI 249263000 and 352003668) 1,888 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 3, 2026, 07:22 UTC | Draught change Reported draught went from 8.2 m to 10.6 m while in port at Amsterdam. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
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 MANA KAI?
- MANA KAI is a sailing vessel sailing under the flag of Malta, built in 2008. The vessel is 183 m long with a beam of 32 m and has a gross tonnage of 30,123.
- Who is recorded as the owner or manager of MANA KAI?
- BESIKTAS LIKID TASIMACILIK DENIZCILIK TICARET A.S. is recorded as ISM manager for MANA KAI (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 Voydar hold for MANA KAI?
- Voydar has no matched sanctions record displayed for MANA KAI 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. MANA KAI has 23 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
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
More Sailing vessels
Other sailing vessels with full Voydar profiles. A different set each day. All sailing vessels
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/9396787Cite this page
MANA KAI. Voydar (voydar.com). https://www.voydar.com/vessel/9396787-mana-kai. 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.