ANNETTE ESSBERGER
Chemical tanker · Portugal · built 2006 · AIS Class A
In short
ANNETTE ESSBERGER (Chemical tanker, Portugal flag) was last seen on AIS on , moored, in the port of Botlek. Its crew-entered AIS destination is NL RTM>NL RTM, with an ETA of Oct 6, 2026, 10:00 UTC; its reported draught is 6.9 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 14:00 UTC). It arrived there on Oct 6, 2026, 10:44 UTC. ISM manager: John T. Essberger GmbH & CO. KG (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Chemical tanker
- Flag
- Portugal
- Year built
- 2006
- Gross tonnage
- 7,903
- Size (length × beam)
- 126 m × 19 m
- ISM manager
- John T. Essberger GmbH & CO. KG
Watch this ship
Get an email when ANNETTE ESSBERGER 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
- 51.8813° N, 4.2679° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 166°
- Heading
- 72°
Last 30 days: 8 port calls (Botlek, Rotterdam, Brunsbuttel, Holtenau, Muuga, Kiel, and Budelsdorf).
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
- ANNETTE ESSBERGER
- IMO numberWhat is an IMO number?
- 9327059
- MMSIWhat is an MMSI?
- 255806303
- Call signWhat is a call sign?
- CQAX5
- Flag
- Portugal
- Vessel type
- Chemical tanker
- AIS ship type
- Tanker
- Gross tonnageGross tonnage vs deadweight
- 7,903
- Deadweight (DWT)
- Source: Wikidata, record Q83640312. Added to Voydar on September 23, 2026. Licence: CC0 1.0.11,340 t
- Length overall
- 126 m
- Beam
- 19 m
- Year built
- 2006
PortugalA 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
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 BotlekAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left RotterdamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at RotterdamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left BotlekAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BotlekAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from New YorkAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at New YorkAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from MATAGORDA SHIP CHANNEL, TX (PORT LAVACA/POINT COMFORT, TX)Authority-reported | USACE foreign traffic vessel entrances & clearances |
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 | 11,586 t | 3,614 t | 230 days | 283 kg |
| 2019 | 9,673 t | 3,017 t | 204 days | 243 kg |
| 2020 | 10,814 t | 3,373 t | 203 days | 220 kg |
| 2021 | 10,589 t | 3,303 t | 162 days | 261 kg |
| 2022 | 10,477 t | 3,268 t | 195 days | 237 kg |
| 2023 | 11,199 t | 3,493 t | 170 days | 264 kg |
| 2024 | 9,960 t | 3,107 t | 153 days | 249 kg |
| 2025 | 9,906 t | 3,090 t | 177 days | 217 kg |
Technical efficiency: EIV (17.1 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 |
|---|---|---|---|
| Botlek NLBOT | Oct 6, 2026, 10:44 UTC | in port | — |
| Rotterdam NLRTM | Oct 3, 2026, 17:58 UTC | Oct 6, 2026, 10:26 UTC | 2 d 16 h |
| Botlek NLBOT | Oct 2, 2026, 19:24 UTC | Oct 3, 2026, 17:32 UTC | 22 h 8 min |
| Brunsbuttel DEBRB | Oct 1, 2026, 12:07 UTC | Oct 1, 2026, 13:10 UTC | 1 h 3 min |
| Holtenau DEHTU | Oct 1, 2026, 02:52 UTC | Oct 1, 2026, 04:34 UTC | 1 h 42 min |
| Muuga EEMUG | Sep 25, 2026, 11:58 UTC | Sep 26, 2026, 00:39 UTC | 12 h 41 min |
| Kiel DEKEL | Sep 23, 2026, 06:33 UTC | Sep 23, 2026, 07:18 UTC | 45 min |
| Budelsdorf DEUSF | Sep 23, 2026, 02:25 UTC | Sep 23, 2026, 04:13 UTC | 1 h 48 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 |
|---|---|---|---|---|
| New York USNYC | Departure | Apr 27, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Arrival | Apr 26, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| MATAGORDA SHIP CHANNEL, TX (PORT LAVACA/POINT COMFORT, TX) | Departure | Apr 7, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| MATAGORDA SHIP CHANNEL, TX (PORT LAVACA/POINT COMFORT, TX) | Arrival | Apr 7, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Departure | May 14, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Arrival | May 14, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Boston USBOS | Departure | May 12, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Boston USBOS | Arrival | May 12, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Aug 28, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Aug 27, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: August 27, 2006.
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 |
|---|---|---|
| Oct 3, 2026, 15:52 UTC | Draught change Reported draught went from 5.8 m to 6.8 m while in port at Botlek. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 25, 2026, 23:22 UTC | Draught change Reported draught went from 8.2 m to 7.4 m while in port at Muuga. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.
Source: Fintraffic / digitraffic.fi, license CC 4.0 BY. Licence: CC BY 4.0.
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 ANNETTE ESSBERGER now?
- ANNETTE ESSBERGER (Chemical tanker, Portugal flag) was last seen on AIS on Oct 6, 2026, 14:33 UTC, moored, in the port of Botlek. The crew-entered destination was NL RTM>NL RTM (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 14:00 UTC). This report does not confirm the ship’s current route.
- What kind of ship is ANNETTE ESSBERGER?
- ANNETTE ESSBERGER is a chemical tanker sailing under the flag of Portugal, built in 2006. The vessel is 126 m long with a beam of 19 m and has a gross tonnage of 7,903.
- Who is recorded as the owner or manager of ANNETTE ESSBERGER?
- John T. Essberger GmbH & CO. KG is recorded as ISM manager for ANNETTE ESSBERGER (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 ANNETTE ESSBERGER?
- Voydar has no matched sanctions record displayed for ANNETTE ESSBERGER 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 ANNETTE ESSBERGER. Missing records do not establish whether the ship has been detained.
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/9327059Using 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.