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 Eemshaven. Its crew-entered AIS destination is SURVEY_ZONE; its reported draught is 1.1 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 14:09 UTC). It arrived there on Oct 2, 2026, 14:11 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.
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.
We email you a link and a code. That creates a free account, no password or card, and follows DEEP NORDIC.
Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.
By continuing you accept the Terms and the Privacy policy.
Last reported position
received- Position
- 53.4444° N, 6.8264° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 0 kn
- Course
- —
- Heading
- —
Last 30 days: at least 12 port calls (Eemshaven, Delfzijl, Landskrona, Makkum, Kiel, Brunsbuttel, Terneuzen, Gent (Ghent), Wieringen/Den Oever, and 't Horntje).
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)
Try the live demo, no sign-upIdentity & particulars
- 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 September 23, 2026. Licence: CC0 1.0.4,500 t
- Length overall
- 90 m
- Beam
- 14.4 m
- Year built
- 2011
NetherlandsA 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 · confidence 0.9 · retrieved Oct 1, 2026
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026HANGZHOU DONG FENG SHIPYARD(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 |
|---|---|---|
| Arrived at EemshavenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left DelfzijlAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at DelfzijlAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left LandskronaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Call sign changed from PCJX to PEDG | AIS, seen by Voydar | |
| Arrived at LandskronaAIS-detected | Voydar port-call detector (AIS geofence) | |
| 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 |
|---|---|---|---|
| Eemshaven NLEEM | Oct 2, 2026, 14:11 UTC | in port | — |
| Delfzijl NLDZL | Oct 1, 2026, 05:29 UTC | Oct 1, 2026, 06:51 UTC | 1 h 21 min |
| Landskrona SELAA | Sep 29, 2026, 09:10 UTC | Sep 30, 2026, 08:43 UTC | 23 h 33 min |
| Makkum NLMAK | Sep 29, 2026, 07:15 UTC | Sep 29, 2026, 09:10 UTC | 1 h 55 min |
| Landskrona SELAA | Sep 28, 2026, 13:30 UTC | Sep 29, 2026, 07:15 UTC | 17 h 45 min |
| Kiel DEKEL | Sep 27, 2026, 19:12 UTC | Sep 27, 2026, 20:18 UTC | 1 h 6 min |
| Brunsbuttel DEBRB | Sep 27, 2026, 09:36 UTC | Sep 27, 2026, 10:28 UTC | 51 min |
| Terneuzen NLTNZ | Sep 25, 2026, 23:15 UTC | Sep 26, 2026, 01:13 UTC | 1 h 58 min |
| Gent (Ghent) BEGNE | Sep 24, 2026, 02:44 UTC | Sep 25, 2026, 21:10 UTC | 42 h 25 min |
| Wieringen/Den Oever NLWRG | Sep 23, 2026, 06:51 UTC | Sep 23, 2026, 10:24 UTC | 3 h 33 min |
| 't Horntje NLTHE | Sep 22, 2026, 08:37 UTC | Sep 22, 2026, 09:32 UTC | 54 min |
| Wieringen/Den Oever NLWRG | Sep 22, 2026, 05:31 UTC | Sep 22, 2026, 08:36 UTC | 3 h 5 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 |
|---|---|---|
| Oct 2, 2026, 06:28 UTC | Draught change Reported draught went from 3.9 m to 1.1 m after leaving Delfzijl. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 2, 2026, 00:00 UTC | IMO used twice IMO 9356567 was broadcast by two ships (MMSI 246782000 and 246820000) 306 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 1, 2026, 17:58 UTC | Draught change Reported draught went from 1.1 m to 3.9 m after leaving Delfzijl. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 1, 2026, 05:32 UTC | Draught change Reported draught went from 3.9 m to 1.1 m while in port at Delfzijl. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Sep 30, 2026, 20:51 UTC | Draught change Reported draught went from 1.1 m to 3.9 m after leaving Landskrona. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 30, 2026, 16:50 UTC | Two positions This MMSI was reported in two places 433 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 30, 2026, 16:32 UTC | Two positions This MMSI was reported in two places 433 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 30, 2026, 14:19 UTC | Draught change Reported draught went from 3.9 m to 1.1 m after leaving Landskrona. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 30, 2026, 12:33 UTC | Two positions This MMSI was reported in two places 543 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 30, 2026, 12:17 UTC | Two positions This MMSI was reported in two places 551 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 30, 2026, 12:03 UTC | Two positions This MMSI was reported in two places 556 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 30, 2026, 11:46 UTC | Two positions This MMSI was reported in two places 564 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 30, 2026, 10:04 UTC | Two positions This MMSI was reported in two places 597 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 30, 2026, 09:47 UTC | Two positions This MMSI was reported in two places 599 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 30, 2026, 09:32 UTC | Two positions This MMSI was reported in two places 598 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 30, 2026, 09:04 UTC | Two positions This MMSI was reported in two places 598 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 30, 2026, 08:46 UTC | Two positions This MMSI was reported in two places 591 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 29, 2026, 07:47 UTC | Draught change Reported draught went from 1.1 m to 5.9 m while in port at Makkum. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Sep 23, 2026, 14:13 UTC | Draught change Reported draught went from 1.1 m to 4 m after leaving Wieringen/Den Oever. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 23, 2026, 02:22 UTC | Two positions This MMSI was reported in two places 550 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict 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
- Where is DEEP NORDIC now?
- DEEP NORDIC (General cargo ship, Netherlands flag) was last seen on AIS on Oct 2, 2026, 14:46 UTC, not moving, in the port of Eemshaven. The crew-entered destination was SURVEY_ZONE (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 14:09 UTC). This report does not confirm the ship’s current route.
- 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 and the New Zealand Russia Sanctions 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.
Sister ships
Likely sister ships: built by Veka Shipyard Lemmer, same type, gross tonnage within 2.5% and length within 1.5% of this ship's.
- RIX BALTICIMO 9250414General cargo ship · built 2002 · 2,999 GT
- StroombankIMO 9356543General cargo ship · built 2009 · 2,999 GT
- Frakt VikIMO 9356579Cargo ship · built 2010 · 2,999 GT
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/9356567Using 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.