HANZE GDANSK
Bulk carrier · Netherlands · built 2013 · AIS Class A
In short
HANZE GDANSK (Bulk carrier, Netherlands flag) was last seen on AIS on , moored, near Syra (Syros) (Mediterranean Sea). Its crew-entered AIS destination is GR JSY (Syra (Syros)); its reported draught is 6.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 13:51 UTC). Registered owner: General Partner ms Hanze Gdansk B.V. (source: ILT — Nederlands vlagregister (Netherlands flag register data)).
- Vessel type
- Bulk carrier
- Flag
- Netherlands
- Year built
- 2013
- Gross tonnage
- 24,210
- Size (length × beam)
- 180 m × 30 m
- Registered owner
- General Partner ms Hanze Gdansk B.V.
Watch this ship
Get an email when HANZE GDANSK reaches Syra (Syros), 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.

Last reported position
received- Position
- 37.4358° N, 24.9402° E
- Area
- Mediterranean Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 315°
- Heading
- 141°
Voydar detected no port call in the last 30 days.
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
- HANZE GDANSK
- IMO numberWhat is an IMO number?
- 9605188
- MMSIWhat is an MMSI?
- 246894000
- Call signWhat is a call sign?
- PCRT
- Flag
- Netherlands
- Vessel type
- Bulk carrier
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 24,210
- Deadweight (DWT)
- Source: Wikidata, record Q83640936. Added to Voydar on September 23, 2026. Licence: CC0 1.0.34,719 t
- Length overall
- 180 m
- Beam
- 30.1 m
- Year built
- 2013
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.
- Registered owner
- General Partner ms Hanze Gdansk B.V.(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · confidence 0.9 · retrieved Oct 1, 2026
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Oct 5, 2026
- Builder
- JIANGSU DAODA MARINE HEAVY INDUSTRY CO. LTD.(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · confidence 0.9 · retrieved Oct 1, 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 |
|---|---|---|
| Former name: UNIGALAXY | AIS, seen by Voydar | |
| Reported departure from BeaumontAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at BeaumontAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from Port ArthurAuthority-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.
Former and other names
Names attested for this ship other than its current name.
| Name | Evidence | Date | Source |
|---|---|---|---|
| UNIGALAXY | Former name, change seen on AIS | Sep 23, 2026 | AIS (vessel's own broadcast) |
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.
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 | 5,998 t | 1,898 t | 103 days | 240 kg |
| 2019 | 5,418 t | 1,716 t | 112 days | 244 kg |
| 2020 | 4,858 t | 1,551 t | 76 days | 221 kg |
| 2021 | 2,728 t | 865 t | 38 days | 281 kg |
| 2022 | 2,848 t | 909 t | 41 days | 259 kg |
| 2023 | 6,176 t | 1,970 t | 107 days | 270 kg |
| 2024 | 5,243 t | 1,674 t | 86 days | 250 kg |
| 2025 | 2,081 t | 667 t | 34 days | 257 kg |
Technical efficiency: EEXI (5.17 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Beaumont USBPT | Departure | Nov 18, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Arrival | Oct 27, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Departure | Nov 16, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Arrival | Nov 15, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Apr 1, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Mar 30, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Departure | Feb 4, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Arrival | Jan 16, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: January 16, 2014.
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 HANZE GDANSK now?
- HANZE GDANSK (Bulk carrier, Netherlands flag) was last seen on AIS on Oct 6, 2026, 14:32 UTC, moored, near Syra (Syros) (Mediterranean Sea). The crew-entered destination was GR JSY (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 13:51 UTC). This report does not confirm the ship’s current route.
- What kind of ship is HANZE GDANSK?
- HANZE GDANSK is a bulk carrier sailing under the flag of Netherlands, built in 2013. The vessel is 180 m long with a beam of 30.1 m and has a gross tonnage of 24,210.
- Who is recorded as the owner or manager of HANZE GDANSK?
- General Partner ms Hanze Gdansk B.V. is recorded as Registered owner for HANZE GDANSK (source: ILT — Nederlands vlagregister (Netherlands flag register data)). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for HANZE GDANSK?
- Voydar has no matched sanctions record displayed for HANZE GDANSK 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 HANZE GDANSK. 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/9605188Using 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.