NEPTUNE KALLOS
Car carrier · Malta · built 2010 · AIS Class A
In short
NEPTUNE KALLOS (Car carrier, Malta flag) was last seen on AIS on , moored, in the port of Haifa. Its crew-entered AIS destination is ILHFA (Haifa), with an ETA of Oct 6, 2026, 00:30 UTC; its reported draught is 8.7 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 10:46 UTC). It arrived there on Oct 6, 2026, 03:07 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
- 2010
- Gross tonnage
- 36,711
- Size (length × beam)
- 168 m × 28 m
Watch this ship
Get an email when NEPTUNE KALLOS arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
Free forever. No card. A free account follows up to 5 ships and ports.

Last reported position
received- Position
- 32.8206° N, 35.0023° E
- Area
- Mediterranean Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 212°
- Heading
- 141°
Last 30 days: 3 port calls (Haifa, Piraeus, and Koper).
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 KALLOS
- IMO numberWhat is an IMO number?
- 9442122
- MMSIWhat is an MMSI?
- 256010000
- Call signWhat is a call sign?
- 9HA5657
- Flag
- Malta
- Vessel type
- Detailed type from WikidataCar carrier
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 36,711
- Deadweight (DWT)
- Source: Wikidata, record Q105767727. Added to Voydar on September 23, 2026. Licence: CC0 1.0.11,215 t
- Length overall
- 168 m
- Beam
- 28 m
- Year built
- 2010
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 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 |
|---|---|---|
| Arrived at HaifaAIS-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) | |
| Left KoperAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KoperAIS-detected | Voydar port-call detector (AIS geofence) | |
| Port State Control inspection at PORTLAND, Oregon | USCG PSIX / CGMIX inspections | |
| Inspection at Portland, Oregon | USCG PSIX / CGMIX inspections | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Port State Control inspection at Santa Barbara, California | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at San Diego, California | 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 |
|---|---|---|---|
| Dec 9, 2020 | Vessel InspectionPSC | PORTLAND, Oregon | clean |
| Dec 8, 2020 | Vessel Operational Control | Portland, Oregon | clean |
| Jul 28, 2011 | Vessel InspectionPSC | Santa Barbara, California | clean |
| Jul 28, 2010 | Vessel InspectionPSC | San Diego, California | 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 |
|---|---|---|---|---|
| 2022 | 10,190 t | 3,231 t | 111 days | 309 kg |
| 2023 | 17,955 t | 5,754 t | 218 days | 296 kg |
| 2024 | 17,705 t | 5,681 t | 195 days | 284 kg |
| 2025 | 13,780 t | 4,400 t | 186 days | 231 kg |
Technical efficiency: EEXI (19.03 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 |
|---|---|---|---|
| Haifa ILHFA | Oct 6, 2026, 03:07 UTC | in port | — |
| Piraeus GRPIR | Oct 3, 2026, 03:47 UTC | Oct 3, 2026, 16:28 UTC | 12 h 41 min |
| Koper SIKOP | Sep 28, 2026, 02:37 UTC | Sep 30, 2026, 19:22 UTC | 2 d 16 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 |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival(matched by call sign) | Apr 13, 2020, 07:48 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Mar 16, 2020, 00:01 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Feb 17, 2020, 13:34 UTC | KC1 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jan 20, 2020, 00:59 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Nov 18, 2019, 05:38 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Oct 21, 2019, 00:47 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Sep 24, 2019, 06:30 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Aug 26, 2019, 06:51 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jul 29, 2019, 01:34 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jul 1, 2019, 07:28 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jun 3, 2019, 04:32 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Boston USBOS | Departure | Jun 22, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: July 28, 2010.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is NEPTUNE KALLOS now?
- NEPTUNE KALLOS (Car carrier, Malta flag) was last seen on AIS on Oct 6, 2026, 11:03 UTC, moored, in the port of Haifa. The crew-entered destination was ILHFA (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 10:46 UTC). This report does not confirm the ship’s current route.
- What kind of ship is NEPTUNE KALLOS?
- NEPTUNE KALLOS is a car carrier sailing under the flag of Malta, built in 2010 by HD Hyundai Mipo. The vessel is 168 m long with a beam of 28 m and has a gross tonnage of 36,711.
- Who is recorded as the owner or manager of NEPTUNE KALLOS?
- Neptune Lines Shipping and Managing Enterprises SA is recorded as ISM manager for NEPTUNE KALLOS (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 KALLOS?
- Voydar has no matched sanctions record displayed for NEPTUNE KALLOS 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. NEPTUNE KALLOS has 4 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
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/9442122Using 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.