ZUIDERDIEP
Cargo ship · Netherlands · AIS Class A
In short
ZUIDERDIEP (Cargo ship, Netherlands flag) was last seen on AIS on , moored, in the North Sea. Its crew-entered AIS destination is HOUTRIBHOOGTE, with an ETA of Nov 19, 2026, 19:22 UTC; its reported draught is 3.5 m (voyage report via AISstream.io global terrestrial AIS, received Nov 20, 2026, 13:45 UTC).
Current voyage: from Amsterdam (departed Nov 18, 2026, 13:19 UTC) to HOUTRIBHOOGTE
- Vessel type
- Cargo ship
- Flag
- Netherlands
- Year built
- —
- Gross tonnage
- —
- Size, AIS-reported (length × beam)
- 86 m × 9 m
- Registered owner
- —
Last reported position: 52.5072° N, 5.4242° E · North Sea · See on the map
Watch this ship
Get an email when ZUIDERDIEP arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 20, 2026, 15:17 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for ZUIDERDIEP reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans
Get alerts on your phone: the Voydar app
Last reported position
received- Position
- 52.5072° N, 5.4242° E
- Area
- North Sea
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 180°
- Heading
- —
- Compass: course over ground 180°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 3 port calls (Amsterdam).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows ZUIDERDIEP's track before the last 30 days. Voydar has recorded its port calls since June 18, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
- Name
- ZUIDERDIEP
- IMO numberWhat is an IMO number?
- —
- MMSIWhat is an MMSI?
- 244710896
- Call signWhat is a call sign?
- PF7371
- Flag
- Netherlands
- Vessel type
- Cargo ship
- Gross tonnageGross tonnage vs deadweight
- —
- Length (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 20, 2026.86 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 20, 2026.9 m
- 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.
AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via AISstream.io global terrestrial AIS on November 20, 2026.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
No owner, operator or manager is recorded for this vessel yet.
Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →
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 |
|---|---|---|
| Left AmsterdamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at AmsterdamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left AmsterdamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at AmsterdamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left AmsterdamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at AmsterdamAIS-detected | Voydar port-call detector (AIS geofence) |
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.
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 |
|---|---|---|---|
| Amsterdam NLAMS | Nov 17, 2026, 22:15 UTC | Nov 18, 2026, 13:19 UTC | 15 h 4 min |
| Amsterdam NLAMS | Oct 26, 2026, 19:41 UTC | Oct 27, 2026, 06:11 UTC | 10 h 30 min |
| Amsterdam NLAMS | Oct 26, 2026, 11:26 UTC | Oct 26, 2026, 12:25 UTC | 59 min |
| Amsterdam NLAMS | Oct 5, 2026, 19:00 UTC | Oct 6, 2026, 10:35 UTC | 15 h 35 min |
| Amsterdam NLAMS | Sep 14, 2026, 20:24 UTC | Sep 15, 2026, 05:18 UTC | 8 h 54 min |
| Amsterdam NLAMS | Sep 14, 2026, 06:55 UTC | Sep 14, 2026, 08:49 UTC | 1 h 54 min |
| Amsterdam NLAMS | Sep 9, 2026, 11:53 UTC | Sep 9, 2026, 13:44 UTC | 1 h 51 min |
| Dordrecht NLDOR | Jul 18, 2026, 02:26 UTC | Jul 22, 2026, 23:42 UTC | 4 d 21 h |
| Vlaardingen NLVLA | Jul 10, 2026, 10:49 UTC | Jul 10, 2026, 14:49 UTC | 4 h 0 min |
| Dordrecht NLDOR | Jun 25, 2026, 20:50 UTC | Jun 29, 2026, 05:59 UTC | 3 d 9 h |
| Amsterdam NLAMS | Jun 18, 2026, 23:31 UTC | Jun 19, 2026, 05:32 UTC | 6 h 1 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.
| When | What we observed | Confidence |
|---|---|---|
| Sep 27, 2026, 18:47 UTC | Alongside another ship Stayed within 89 m of GROVA at low speed for 9 h 0 min, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. GROVA →Method seadar.behaviour.sts_candidate v1 | Medium (70%) |
| Sep 27, 2026, 17:17 UTC | Alongside another ship Stayed within 91 m of TMS PIA at low speed for 10 h 30 min, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. TMS PIA →Method seadar.behaviour.sts_candidate v1 | Medium (70%) |
| Sep 26, 2026, 22:47 UTC | Alongside another ship Stayed within 59 m of HEIDI REICH at low speed for 5 h 10 min, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. HEIDI REICH →Method seadar.behaviour.sts_candidate v1 | Medium (70%) |
| Sep 26, 2026, 18:27 UTC | Alongside another ship Stayed within 187 m of TMS PIA at low speed for 9 h 30 min, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. TMS PIA →Method seadar.behaviour.sts_candidate v1 | Medium (60%) |
| Sep 26, 2026, 14:47 UTC | Alongside another ship Stayed within 61 m of HAMARITHA at low speed for 37 h 0 min, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. HAMARITHA →Method seadar.behaviour.sts_candidate v1 | Medium (70%) |
| Sep 26, 2026, 12:17 UTC | Alongside another ship Stayed within 94 m of VENTRANS II at low speed for 21 h 20 min, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. VENTRANS II →Method seadar.behaviour.sts_candidate v1 | Medium (70%) |
| Sep 26, 2026, 10:27 UTC | Alongside another ship Stayed within 192 m of HAMARITHA at low speed for 3 h 10 min, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. HAMARITHA →Method seadar.behaviour.sts_candidate v1 | Medium (50%) |
| Sep 25, 2026, 14:27 UTC | Alongside another ship Stayed within 152 m of CLAUDIA at low speed for 2 d 12 h, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. CLAUDIA →Method seadar.behaviour.sts_candidate v1 | Medium (60%) |
| Sep 25, 2026, 14:07 UTC | Alongside another ship Stayed within 37 m of ALPA at low speed for 2 d 13 h, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. ALPA →Method seadar.behaviour.sts_candidate v1 | Medium (70%) |
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
- What kind of ship is ZUIDERDIEP?
- ZUIDERDIEP is a cargo ship sailing under the flag of Netherlands.
- What sanctions and inspection records does Voydar hold for ZUIDERDIEP?
- Voydar has no matched sanctions record displayed for ZUIDERDIEP 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 ZUIDERDIEP. Missing records do not establish whether the ship has been detained.
More Cargo ships
Other cargo ships with full Voydar profiles, those under the flag of Netherlands first. A different set each day. All cargo ships
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/mmsi-244710896Cite this page
ZUIDERDIEP. Voydar (voydar.com). https://www.voydar.com/vessel/mmsi-244710896-zuiderdiep. Retrieved November 20, 2026.
Each fact above names its own source and date. Cite that primary source too when you rely on a fact.
Using this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.