DEEP NORDIC
General cargo ship · Netherlands · built 2011 · AIS Class A
In short
DEEP NORDIC (General cargo ship, Netherlands flag) was last seen on AIS on , not moving, in the port of Terneuzen. Its crew-entered AIS destination is SURVEY_ZONE; its reported draught is 1.1 m (voyage report via AISstream.io global terrestrial AIS, received Nov 17, 2026, 17:18 UTC). It arrived there on Nov 16, 2026, 14:24 UTC. Registered owner: Cederborg B.V. (source: ILT — Nederlands vlagregister (Netherlands flag register data)).
- Vessel type
- General cargo ship
- Flag
- Netherlands
- Year built
- 2011
- Gross tonnage
- 2,999
- Size (length × beam)
- 90 m × 14 m
- Registered owner
- Cederborg B.V.

Last reported position: 51.3408° N, 3.8275° E · North Sea · See on the map
Watch this ship
Get an email when DEEP NORDIC 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:50 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for DEEP NORDIC 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
- 51.3408° N, 3.8275° E
- Area
- North Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- —
- Heading
- —
Locator map: Natural Earth (public domain)
Last 30 days: at least 12 port calls (Terneuzen, Skagen, Nieuwdorp, Roytta, Ajos, Hundested, Valberg, and Aarhus).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Data delivered by BarentsWatch
A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 90 mone tick every 10 m
Beam 14.4 mPlan outline, to scale
- Name
- DEEP NORDIC
- IMO numberWhat is an IMO number?
- 9356567
- MMSIWhat is an MMSI?
- 246820000
- Call signWhat is a call sign?
- PEDG
- Flag
- Netherlands
- AIS ship type
- High-speed craft (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- 2,999
- Deadweight (DWT)
- Source: Wikidata, record Q105765746. Added to Voydar on October 23, 2026. Licence: CC0 1.0.4,500 t
- Length overall
- 90 m
- Beam
- 14.4 m
- Year built
- 2011
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
- Cederborg B.V.(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · high confidence · retrieved Nov 12, 2026
- Builder
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026HANGZHOU DONG FENG SHIPYARD(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · high confidence · retrieved Nov 12, 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 |
|---|---|---|
| Arrived at TerneuzenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left TerneuzenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at TerneuzenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SkagenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SkagenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Tornea (Tornio)Authority-reported | Digitraffic Port Call API | |
| Reported arrival at Tornea (Tornio)Authority-reported | Digitraffic Port Call API | |
| Reported departure from Kemi/Tornea (Kemi/Tornio)Authority-reported | Digitraffic Port Call API | |
| Reported arrival at Kemi/Tornea (Kemi/Tornio)Authority-reported | Digitraffic Port Call API | |
| Call sign changed from PCJX to PEDG | AIS, seen by Voydar | |
| Former name: CEDERBORG | AIS, seen by Voydar | |
| Call sign changed from PEDG to PCJX | AIS, seen by Voydar |
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 |
|---|---|---|---|
| CEDERBORG | Former name, change seen on AIS | Sep 22, 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.
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 |
|---|---|---|---|
| Terneuzen NLTNZ | Nov 16, 2026, 14:24 UTC | in port | — |
| Terneuzen NLTNZ | Nov 14, 2026, 16:18 UTC | Nov 16, 2026, 09:45 UTC | 41 h 27 min |
| Skagen DKSKA | Nov 8, 2026, 16:57 UTC | Nov 8, 2026, 20:50 UTC | 3 h 53 min |
| Terneuzen NLTNZ | Nov 5, 2026, 11:08 UTC | Nov 14, 2026, 07:37 UTC | 8 d 20 h |
| Nieuwdorp NLNIU | Nov 5, 2026, 07:40 UTC | Nov 5, 2026, 08:45 UTC | 1 h 5 min |
| Roytta FIROY | Nov 3, 2026, 15:42 UTC | Nov 4, 2026, 13:37 UTC | 21 h 54 min |
| Ajos FIAJO | Nov 2, 2026, 12:44 UTC | Nov 3, 2026, 14:22 UTC | 25 h 38 min |
| Terneuzen NLTNZ | Oct 28, 2026, 15:44 UTC | Nov 5, 2026, 06:34 UTC | 7 d 14 h |
| Nieuwdorp NLNIU | Oct 28, 2026, 10:50 UTC | Oct 28, 2026, 12:00 UTC | 1 h 10 min |
| Hundested DKHUN | Oct 27, 2026, 08:21 UTC | Oct 27, 2026, 17:55 UTC | 9 h 35 min |
| Valberg NOVBE | Oct 23, 2026, 11:01 UTC | Oct 26, 2026, 07:22 UTC | 2 d 20 h |
| Aarhus DKAAR | Oct 21, 2026, 12:16 UTC | Oct 22, 2026, 14:38 UTC | 26 h 21 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 |
|---|---|---|---|---|
| Tornea (Tornio) FITOR | Arrival | Nov 3, 2026, 15:59 UTC | Kaksi | Digitraffic Port Call API |
| Kemi/Tornea (Kemi/Tornio) FIKEM | Arrival | Nov 2, 2026, 12:50 UTC | LAITURI 6 | Digitraffic Port Call API |
Records published by the authority named on each row. Earliest record for this ship: November 2, 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 17, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 1,741 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 16, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 1,825 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 15, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 1,936 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 11, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 339 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 10, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 107 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 9, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 786 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 8, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 827 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 7, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 749 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 6, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 1,113 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 5, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 1,425 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 4, 2026, 07:44 UTC | Draught change Reported draught went from 3.8 m to 5.8 m while in port at Roytta. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Nov 4, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 1,812 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 3, 2026, 11:15 UTC | Draught change Reported draught went from 5.1 m to 3.8 m while in port at Ajos. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 3, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 1,975 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 2, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 1,980 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 1, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 1,716 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 31, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 1,368 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 28, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 725 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 27, 2026, 19:18 UTC | Draught change Reported draught went from 6.3 m to 3.6 m after leaving Hundested. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 27, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 758 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.
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
- What kind of ship is DEEP NORDIC?
- DEEP NORDIC is a general cargo ship sailing under the flag of Netherlands, built in 2011 by Veka Shipyard Lemmer. The vessel is 90 m long with a beam of 14.4 m and has a gross tonnage of 2,999.
- Who is recorded as the owner or manager of DEEP NORDIC?
- Cederborg B.V. is recorded as Registered owner for DEEP NORDIC (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 DEEP NORDIC?
- Voydar has no matched sanctions record displayed for DEEP NORDIC 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 DEEP NORDIC. 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
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/9356567Cite this page
DEEP NORDIC. Voydar (voydar.com). https://www.voydar.com/vessel/9356567-deep-nordic. 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.