Neptune Kefalonia
Car carrier · Malta · built 2009 · AIS Class A
In short
Neptune Kefalonia (Car carrier, Malta flag) was last seen on AIS on , not moving, in the port of Piraeus. Its crew-entered AIS destination is GRPIR (Piraeus), with an ETA of Nov 20, 2026, 06:00 UTC; its reported draught is 8.7 m (voyage report via AISstream.io global terrestrial AIS, received Nov 20, 2026, 12:23 UTC). It arrived there on Nov 20, 2026, 06:19 UTC. ISM manager: Neptune Lines Shipping and Managing Enterprises SA (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Car carrier
- Flag
- Malta
- Year built
- 2009
- Gross tonnage
- 36,825
- Size (length × beam)
- 170 m × 28 m

Last reported position: 37.9591° N, 23.6059° E · Mediterranean Sea · See on the map
Shipping a car on this vessel?
Follow Neptune Kefalonia and Voydar's daily email tells you when it has arrived in port, left again, or changed its destination.
What you would have been told
Following Neptune Kefalonia over the last 24 hours would have sent 1 message.
- ArrivedPiraeus
Detected from AIS, as of Nov 20, 2026, 12:38 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Neptune Kefalonia 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: the Voydar app
Last reported position
received- Position
- 37.9591° N, 23.6059° E
- Area
- Mediterranean Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 329°
- Heading
- 222°
- Compass: course over ground 329°, heading 222°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 7 port calls (Piraeus, Fusina, and Koper).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Neptune Kefalonia's track before the last 30 days. Voydar has recorded its port calls since September 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 169.6 mone tick every 25 m
Beam 28 mPlan outline, to scale
- Name
- Neptune Kefalonia
- IMO numberWhat is an IMO number?
- 9438717
- MMSIWhat is an MMSI?
- 215588000
- Call signWhat is a call sign?
- 9HA2117
- Flag
- Malta
- Vessel type
- Detailed type from WikidataCar carrier
- Gross tonnageGross tonnage vs deadweight
- 36,825
- Length overall
- 169.6 m
- Beam
- 28 m
- Year built
- 2009
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
- 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 |
|---|---|---|
| Arrived at PiraeusAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left FusinaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at FusinaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left KoperAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KoperAIS-detected | Voydar port-call detector (AIS geofence) | |
| Call sign changed from 9HA2117 to DATAHUB | AIS, seen by Voydar |
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.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 20,089 t | 6,441 t | 245 days | 291 kg |
| 2019 | 18,169 t | 5,825 t | 217 days | 275 kg |
| 2020 | 15,864 t | 5,085 t | 218 days | 245 kg |
| 2021 | 15,388 t | 4,933 t | 202 days | 242 kg |
| 2022 | 16,242 t | 5,202 t | 193 days | 257 kg |
| 2023 | 16,116 t | 5,164 t | 200 days | 256 kg |
| 2024 | 15,817 t | 5,071 t | 196 days | 256 kg |
| 2025 | 15,553 t | 4,962 t | 202 days | 236 kg |
Technical efficiency: EEXI (18.93 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 “Vehicle carrier”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile59.16 g per tonne-nautical mile
- Lowest reportedHighest reported
53% of the 512 ships in this group reported a lower figure.
Group: lower quartile 42.45 · median 56.04 · upper quartile 87.32
- CO₂ per nautical mile sailed235.9 kg per nautical mile
- Lowest reportedHighest reported
9% of the 514 ships in this group reported a lower figure.
Group: lower quartile 274.3 · median 309.1 · upper quartile 338.7
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 |
|---|---|---|---|
| Piraeus GRPIR | Nov 20, 2026, 06:19 UTC | in port | — |
| Fusina ITFSA | Nov 15, 2026, 10:35 UTC | Nov 17, 2026, 08:30 UTC | 45 h 55 min |
| Koper SIKOP | Nov 10, 2026, 11:38 UTC | Nov 15, 2026, 01:10 UTC | 4 d 13 h |
| Piraeus GRPIR | Nov 7, 2026, 07:06 UTC | Nov 7, 2026, 20:02 UTC | 12 h 55 min |
| Fusina ITFSA | Oct 28, 2026, 06:30 UTC | Oct 30, 2026, 08:23 UTC | 2 d 1 h |
| Koper SIKOP | Oct 26, 2026, 08:21 UTC | Oct 28, 2026, 00:55 UTC | 40 h 34 min |
| Piraeus GRPIR | Oct 23, 2026, 13:36 UTC | Oct 24, 2026, 04:37 UTC | 15 h 1 min |
| Koper SIKOP | Oct 13, 2026, 19:12 UTC | Oct 15, 2026, 05:58 UTC | 34 h 46 min |
| Fusina ITFSA | Oct 11, 2026, 09:36 UTC | Oct 13, 2026, 12:40 UTC | 2 d 3 h |
| Piraeus GRPIR | Oct 4, 2026, 08:26 UTC | Oct 4, 2026, 12:33 UTC | 4 h 6 min |
| Piraeus GRPIR | Oct 4, 2026, 03:10 UTC | Oct 4, 2026, 08:15 UTC | 5 h 5 min |
| Barcelona ESBCN | Sep 29, 2026, 01:56 UTC | Sep 30, 2026, 23:08 UTC | 45 h 12 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.
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 |
|---|---|---|
| Oct 29, 2026, 08:18 UTC | Draught change Reported draught went from 8.7 m to 8.2 m while in port at Fusina. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 12, 2026, 18:16 UTC | Draught change Reported draught went from 8.7 m to 8.2 m while in port at Fusina. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 4, 2026, 16:18 UTC | Two positions This MMSI was reported in two places 848 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 14:50 UTC | Two positions This MMSI was reported in two places 815 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 12:33 UTC | Two positions This MMSI was reported in two places 781 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 12:20 UTC | Two positions This MMSI was reported in two places 782 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 11:32 UTC | Two positions This MMSI was reported in two places 782 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 11:06 UTC | Two positions This MMSI was reported in two places 782 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 10:32 UTC | Two positions This MMSI was reported in two places 782 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 10:02 UTC | Two positions This MMSI was reported in two places 782 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 09:47 UTC | Two positions This MMSI was reported in two places 782 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 09:17 UTC | Two positions This MMSI was reported in two places 782 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 08:51 UTC | Two positions This MMSI was reported in two places 782 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 07:33 UTC | Two positions This MMSI was reported in two places 782 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 07:19 UTC | Two positions This MMSI was reported in two places 782 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 06:16 UTC | Two positions This MMSI was reported in two places 782 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 06:01 UTC | Two positions This MMSI was reported in two places 781 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 05:32 UTC | Two positions This MMSI was reported in two places 781 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 05:03 UTC | Two positions This MMSI was reported in two places 781 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 04:46 UTC | Two positions This MMSI was reported in two places 781 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
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 Neptune Kefalonia?
- Neptune Kefalonia is a car carrier sailing under the flag of Malta, built in 2009 by HD Hyundai Mipo. The vessel is 169.6 m long with a beam of 28 m and has a gross tonnage of 36,825.
- Who is recorded as the owner or manager of Neptune Kefalonia?
- Neptune Lines Shipping and Managing Enterprises SA is recorded as ISM manager for Neptune Kefalonia (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 Neptune Kefalonia?
- Voydar has no matched sanctions record displayed for Neptune Kefalonia 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. No matched inspection records are displayed for Neptune Kefalonia. 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
More Car carriers
Other car carriers with full Voydar profiles. A different set each day. All car carriers
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/9438717Cite this page
Neptune Kefalonia. Voydar (voydar.com). https://www.voydar.com/vessel/9438717-neptune-kefalonia. Retrieved November 20, 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.