SLOMAN HEBE
Chemical tanker · Antigua & Barbuda · AIS Class A
In short
SLOMAN HEBE (Chemical tanker, Antigua & Barbuda flag) was last seen on AIS on , moored, in the port of Port-Jerome. Its crew-entered AIS destination is FRURO>FRPJE; its reported draught is 5.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 01:43 UTC). It arrived there on Oct 1, 2026, 10:28 UTC. ISM manager: Sloman Neptun Schiffahrts-AG (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Chemical tanker
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- ISM manager
- Sloman Neptun Schiffahrts-AG
Watch this ship
Get an email when SLOMAN HEBE arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
We email you a link and a code. That creates a free account, no password or card, and follows SLOMAN HEBE.
Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.
By continuing you accept the Terms and the Privacy policy.
Last reported position
received- Position
- 49.4707° N, 0.5366° E
- Area
- English Channel
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 14°
- Heading
- 322°
Last 30 days: 5 port calls (Port-Jerome, Petit-Couronne, Europoort, and Mongstad).
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)
Try the live demo, no sign-upIdentity & particulars
- Name
- SLOMAN HEBE
- IMO numberWhat is an IMO number?
- 9809784
- MMSIWhat is an MMSI?
- 305265000
- Call signWhat is a call sign?
- V2GX2
- AIS ship type
- Tanker
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- Year built
- —
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 Sep 28, 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 Port-JeromeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Petit-CouronneAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Petit-CouronneAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left EuropoortAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at EuropoortAIS-detected | Voydar port-call detector (AIS geofence) | |
| 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) |
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 |
|---|---|---|---|---|
| 2023 | 4,648 t | 1,453 t | 91 days | 208 kg |
| 2024 | 7,065 t | 2,230 t | 147 days | 187 kg |
| 2025 | 5,902 t | 1,846 t | 119 days | 204 kg |
Technical efficiency: EEXI (7.51 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 |
|---|---|---|---|
| Port-Jerome FRPJE | Oct 1, 2026, 10:28 UTC | in port | — |
| Petit-Couronne FRPET | Sep 28, 2026, 14:51 UTC | Sep 30, 2026, 20:32 UTC | 2 d 5 h |
| Europoort NLEUR | Sep 23, 2026, 20:58 UTC | Sep 25, 2026, 21:24 UTC | 2 d 0 h |
| Mongstad NOMON | Sep 15, 2026, 17:01 UTC | Sep 16, 2026, 18:00 UTC | 24 h 59 min |
| Mongstad NOMON | Sep 9, 2026, 14:23 UTC | Sep 11, 2026, 14:13 UTC | 47 h 49 min |
| Mongstad NOMON | Jul 9, 2026, 15:44 UTC | Jul 10, 2026, 17:07 UTC | 25 h 23 min |
| Lillo BELIL | Jun 14, 2026, 21:02 UTC | Jun 14, 2026, 22:36 UTC | 1 h 35 min |
| Lillo BELIL | Jun 13, 2026, 23:34 UTC | Jun 14, 2026, 21:02 UTC | 21 h 28 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | Nov 16, 2020, 20:04 UTC | SINO | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
Records published by the authority named on each row. Earliest record for this ship: November 16, 2020.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
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 |
|---|---|---|
| Sep 30, 2026, 04:43 UTC | Draught change Reported draught went from 8.9 m to 5.2 m while in port at Petit-Couronne. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Sep 25, 2026, 14:09 UTC | Draught change Reported draught went from 6 m to 6.5 m while in port at Europoort. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
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 SLOMAN HEBE now?
- SLOMAN HEBE (Chemical tanker, Antigua & Barbuda flag) was last seen on AIS on Oct 4, 2026, 02:22 UTC, moored, in the port of Port-Jerome. The crew-entered destination was FRURO>FRPJE (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 01:43 UTC). This report does not confirm the ship’s current route.
- What kind of ship is SLOMAN HEBE?
- SLOMAN HEBE is a chemical tanker sailing under the flag of Antigua & Barbuda.
- Who is recorded as the owner or manager of SLOMAN HEBE?
- Sloman Neptun Schiffahrts-AG is recorded as ISM manager for SLOMAN HEBE (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 SLOMAN HEBE?
- Voydar has no matched sanctions record displayed for SLOMAN HEBE 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 SLOMAN HEBE. Missing records do not establish whether the ship has been detained.
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/9809784Using 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.