Skip to content

ERNST HAGEDORN

General cargo ship · Germany · built 1996 · AIS Class A

IMO9137301MMSI218030270Call signDFUHLast AIS position Oct 5, 2026, 02:55 UTC

In short

ERNST HAGEDORN (General cargo ship, Germany flag) was last seen on AIS on , under way at 7.2 kn, near Nynashamn (Baltic Sea). Its crew-entered AIS destination is SESTV (Stora Vika), with an ETA of Oct 4, 2026, 12:00 UTC; its reported draught is 5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 01:44 UTC). ISM manager: GBS-Shipmanagement GmbH & Co. KG (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Current voyage: from Holtenau (departed Oct 2, 2026, 08:41 UTC) to SESTV (Stora Vika)

Year built
1996
Gross tonnage
1,864
Size (length × beam)
82 m × 11 m

Watch this ship

Get an email when ERNST HAGEDORN reaches Stora Vika, and when it 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.

Photo of ERNST HAGEDORN
Photo: Farid mernissi · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
58.6948° N, 17.8713° E
Area
Baltic Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
7.2 kn
Course
351°
Heading
348°
58.6948° N, 17.8713° E
Open the full live map →

Last 30 days: 4 port calls (Holtenau, Brunsbuttel, Dordrecht, and Ellerbek).

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-up

Identity & particulars

Name
ERNST HAGEDORN
IMO numberWhat is an IMO number?
9137301
MMSIWhat is an MMSI?
218030270
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
1,864
Length overall
82.4 m
Beam
11.5 m
Year built
1996

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 year 2025 · reported · confidence 0.9 · retrieved Sep 28, 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.

DateEventSource
Left HoltenauAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at HoltenauAIS-detectedVoydar port-call detector (AIS geofence)
Left BrunsbuttelAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BrunsbuttelAIS-detectedVoydar port-call detector (AIS geofence)
Left DordrechtAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at DordrechtAIS-detectedVoydar port-call detector (AIS geofence)
Former name: MaremkaWikidata
Former name: TomarWikidata
Former name: AntaresWikidata
Former name: RMS AntaresWikidata

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.

Former and other names

Names attested for this ship other than its current name.

NameEvidenceDateSource
MaremkaFormer nameJan 1, 2016Wikidata
TomarFormer nameJan 1, 2005Wikidata
AntaresFormer nameJan 1, 1999Wikidata
RMS AntaresFormer nameJan 1, 1996Wikidata

A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.

Source: Wikidata. Licence: CC0 1.0.

Emissions & fuel consumption

Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20251,617 t504 t152 days47 kg

Technical efficiency: EEXI (22.99 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

PortArrivedDepartedTime in port
Holtenau DEHTUOct 2, 2026, 07:39 UTCOct 2, 2026, 08:41 UTC1 h 2 min
Brunsbuttel DEBRBOct 1, 2026, 20:56 UTCOct 2, 2026, 00:14 UTC3 h 17 min
Dordrecht NLDORSep 28, 2026, 22:25 UTCSep 30, 2026, 12:34 UTC38 h 9 min
Ellerbek DEELBSep 26, 2026, 23:16 UTCSep 27, 2026, 01:29 UTC2 h 13 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.

WhenWhat we observedConfidence
Sep 30, 2026, 04:39 UTC
Draught change

Reported draught went from 3 m to 4.5 m while in port at Dordrecht. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 25, 2026, 09:24 UTC
Alongside another ship

Stayed within 199 m of AASHEIM at low speed for 7 h 2 min, 17 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed.

AASHEIM →

Method seadar.behaviour.sts_candidate v1

Medium (60%)

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.

How these are computed →

Frequently asked questions

Where is ERNST HAGEDORN now?
ERNST HAGEDORN (General cargo ship, Germany flag) was last seen on AIS on Oct 5, 2026, 02:55 UTC, under way at 7.2 kn, near Nynashamn (Baltic Sea). The crew-entered destination was SESTV (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 01:44 UTC). This report does not confirm the ship’s current route.
What kind of ship is ERNST HAGEDORN?
ERNST HAGEDORN is a general cargo ship sailing under the flag of Germany, built in 1996 by SLKB Komarno – Slovak Shipyard Komárno. The vessel is 82.4 m long with a beam of 11.5 m and has a gross tonnage of 1,864.
Who is recorded as the owner or manager of ERNST HAGEDORN?
GBS-Shipmanagement GmbH & Co. KG is recorded as ISM manager for ERNST HAGEDORN (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for ERNST HAGEDORN?
Voydar has no matched sanctions record displayed for ERNST HAGEDORN 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 ERNST HAGEDORN. 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/9137301
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using 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.

See plans