Neptune Kefalonia
Car carrier · Malta · built 2009 · AIS Class A
In short
Neptune Kefalonia (Car carrier, Malta flag) was last seen on AIS on , under way at 15 kn, near Pozzallo (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 LAST UPDATE TIME; its reported draught is 8.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 14:01 UTC). ISM manager: Neptune Lines Shipping and Managing Enterprises SA (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Piraeus (departed Oct 4, 2026, 12:33 UTC) to LAST UPDATE TIME
- Vessel type
- Car carrier
- Flag
- Malta
- Year built
- 2009
- Gross tonnage
- 36,825
- Size (length × beam)
- 170 m × 28 m
Watch this ship
Neptune Kefalonia has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.
Free forever. No card. A free account follows up to 5 ships and ports.
Last reported position
received- Position
- 36.6054° N, 14.9268° E
- Area
- Mediterranean Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 15 kn
- Course
- 101°
- Heading
- 101°
Last 30 days: 3 port calls (Piraeus and Barcelona).
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)Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- Neptune Kefalonia
- IMO numberWhat is an IMO number?
- 9438717
- MMSIWhat is an MMSI?
- 215588000
- Call signWhat is a call sign?
- DATAHUB
- Flag
- Malta
- Vessel type
- Detailed type from WikidataCar carrier
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 36,825
- Length overall
- 169.6 m
- Beam
- 28 m
- Year built
- 2009
MaltaA 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 Oct 5, 2026
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 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.
| Date | Event | Source |
|---|---|---|
| Left PiraeusAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at PiraeusAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left PiraeusAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at PiraeusAIS-detected | Voydar port-call detector (AIS geofence) | |
| Call sign changed from 9HA2117 to DATAHUB | AIS, seen by Voydar | |
| Left BarcelonaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BarcelonaAIS-detected | Voydar port-call detector (AIS geofence) |
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.
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 | 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 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%) |
| Oct 4, 2026, 04:34 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:18 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
- Where is Neptune Kefalonia now?
- Neptune Kefalonia (Car carrier, Malta flag) was last seen on AIS on Oct 5, 2026, 14:17 UTC, under way at 15 kn, near Pozzallo (Mediterranean Sea). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was LAST UPDATE TIME (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 14:01 UTC). This report does not confirm the ship’s current route.
- 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.
Sister ships
Likely sister ships: built by HD Hyundai Mipo, same type, gross tonnage within 2.5% and length within 1.5% of this ship's.
- Neptune HellasIMO 9440148Car carrier · built 2009 · 36,711 GT
- NEPTUNE PHOSIMO 9451719Car carrier · built 2009 · 36,711 GT
- NEPTUNE HORIZONIMO 9451721Car carrier · built 2010 · 36,711 GT
- Neptune IliadIMO 9440100Car carrier · built 2010 · 36,825 GT
- Neptune IthakiIMO 9440083Car carrier · built 2010 · 36,825 GT
- NEPTUNE KALLOSIMO 9442122Car carrier · built 2010 · 36,711 GT
- NEPTUNE ODYSSEYIMO 9440095Car carrier · built 2010 · 36,902 GT
- Rcc PassionIMO 9453107Car carrier · built 2011 · 36,834 GT
- Rcc PrestigeIMO 9455715Car carrier · built 2011 · 36,834 GT
- Neptune GaleneIMO 9668491Car carrier · built 2014 · 37,602 GT
- Neptune ThalassaIMO 9668506Car carrier · built 2014 · 37,602 GT
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/9438717Using 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.