Nieuwe Diep
Naval vessel · Netherlands · built 1990 · AIS Class A
In short
Nieuwe Diep (Naval vessel, Netherlands flag) was last seen on AIS on , moored, near Den Helder (North Sea). Its crew-entered AIS destination is DEN HELDER; its reported draught is 1.6 m (voyage report via AISstream.io global terrestrial AIS, received Nov 17, 2026, 17:18 UTC).
Current voyage: from Den Helder (departed Oct 23, 2026, 13:06 UTC) to DEN HELDER
- Vessel type
- Naval vessel
- Flag
- Netherlands
- Year built
- 1990
- Gross tonnage
- 288
- Size (length × beam)
- 38 m
- Registered owner
- —

Last reported position: 52.9618° N, 4.7804° E · North Sea · See on the map
Watch this ship
Get an email when Nieuwe Diep 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 17, 2026, 17:49 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Nieuwe Diep 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: Voydar for iPhone
Last reported position
received- Position
- 52.9618° N, 4.7804° E
- Area
- North Sea
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 13°
- Heading
- —
- Compass: course over ground 13°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
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.
Pro shows Nieuwe Diep's track before the last 30 days. Voydar has recorded its port calls since June 15, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 38.2 mone tick every 5 m
- Name
- Nieuwe Diep
- IMO numberWhat is an IMO number?
- 8900799
- MMSIWhat is an MMSI?
- 246223000
- Call signWhat is a call sign?
- PHBV
- Flag
- Netherlands
- Vessel type
- Naval vessel
- Gross tonnageGross tonnage vs deadweight
- 288
- Length overall
- 38.2 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 17, 2026.6 m
- Year built
- 1990
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 17, 2026.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
- Builder
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026
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 Den HelderAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Den HelderAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left CuxhavenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at CuxhavenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left CuxhavenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at CuxhavenAIS-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 |
|---|---|---|---|
| Den Helder NLDHR | Oct 15, 2026, 11:57 UTC | Oct 23, 2026, 13:06 UTC | 8 d 1 h |
| Cuxhaven DECUX | Oct 7, 2026, 10:54 UTC | Oct 15, 2026, 07:07 UTC | 7 d 20 h |
| Cuxhaven DECUX | Oct 6, 2026, 13:25 UTC | Oct 7, 2026, 07:04 UTC | 17 h 38 min |
| Wewelsfleth DEWEW | Oct 6, 2026, 08:31 UTC | Oct 6, 2026, 11:25 UTC | 2 h 54 min |
| Cuxhaven DECUX | Oct 3, 2026, 12:18 UTC | Oct 6, 2026, 06:08 UTC | 2 d 17 h |
| Cuxhaven DECUX | Sep 29, 2026, 06:00 UTC | Sep 30, 2026, 07:29 UTC | 25 h 29 min |
| Cuxhaven DECUX | Sep 23, 2026, 12:53 UTC | Sep 28, 2026, 12:12 UTC | 4 d 23 h |
| Cuxhaven DECUX | Sep 18, 2026, 20:33 UTC | Sep 23, 2026, 07:25 UTC | 4 d 10 h |
| Den Helder NLDHR | Sep 7, 2026, 13:34 UTC | Oct 15, 2026, 11:26 UTC | 37 d 21 h |
| Wewelsfleth DEWEW | Jul 6, 2026, 07:33 UTC | Jul 15, 2026, 06:51 UTC | 8 d 23 h |
| Den Helder NLDHR | Jun 15, 2026, 11:31 UTC | Jun 15, 2026, 12:38 UTC | 1 h 7 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 |
|---|---|---|
| Nov 5, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 275 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 20, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 19, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 17, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 16, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 15, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 14, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 13, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 12, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 11, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 10, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 9, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 7, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 6, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 5, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 4, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 3, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Sep 30, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 273 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Sep 29, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 280 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Sep 28, 2026, 00:00 UTC | IMO used twice IMO 8900799 was broadcast by two ships (MMSI 211196860 and 246223000) 263 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
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 Nieuwe Diep?
- Nieuwe Diep is a naval vessel sailing under the flag of Netherlands, built in 1990 by Damen Shipyards Gorinchem. The vessel is 38.2 m long and has a gross tonnage of 288.
- What sanctions and inspection records does Voydar hold for Nieuwe Diep?
- Voydar has no matched sanctions record displayed for Nieuwe Diep 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 Nieuwe Diep. Missing records do not establish whether the ship has been detained.
Full Vessel Report
A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.
Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.
Every fact on this page stays free.
Know this ship?
Help other readers. Member posts are shown as member content, never as sourced data.
- Date, place and an optional note
- Members who know her can answer
- Suggest a correctionChecked against sources before anything changes
More Naval vessels
Other naval vessels with full Voydar profiles, those under the flag of Netherlands first. A different set each day. All naval vessels
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/8900799Cite this page
Nieuwe Diep. Voydar (voydar.com). https://www.voydar.com/vessel/8900799-nieuwediep. Retrieved November 17, 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.