ZK 4 ALBATROS
Fishing vessel · Netherlands · built 2014 · AIS Class A
In short
ZK 4 ALBATROS (Fishing vessel, Netherlands flag) was last seen on AIS on , not moving, in the North Sea. Its crew-entered AIS destination is GRONINGEN; its reported draught is 1.5 m (voyage report via AISstream.io global terrestrial AIS, received Nov 18, 2026, 02:11 UTC). Registered owner: Van Oord Overig Materieel IV B.V. (source: ILT — Nederlands vlagregister (Netherlands flag register data)).
Current voyage: from IJmuiden/Velsen (departed Oct 31, 2026, 07:03 UTC) to GRONINGEN
- Vessel type
- Fishing vessel
- Flag
- Netherlands
- Year built
- 2014
- Gross tonnage
- 9,675
- Size (length × beam)
- 123 m
- Registered owner
- Van Oord Overig Materieel IV B.V.

Last reported position: 53.3368° N, 6.2994° E · North Sea · See on the map
Watch this ship
Get an email when ZK 4 ALBATROS 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 18, 2026, 02:17 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for ZK 4 ALBATROS 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
- 53.3368° N, 6.2994° E
- Area
- North Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 274°
- Heading
- —
- Compass: course over ground 274°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 5 port calls (IJmuiden/Velsen and Amsterdam).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows ZK 4 ALBATROS's track before the last 30 days. Voydar has recorded its port calls since September 9, 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 122.7 mone tick every 25 m
- Name
- ZK 4 ALBATROS
- IMO numberWhat is an IMO number?
- 9715505
- MMSIWhat is an MMSI?
- 244780712
- Call signWhat is a call sign?
- PF9939
- Flag
- Netherlands
- Vessel type
- Fishing vessel
- Gross tonnageGross tonnage vs deadweight
- 9,675
- Length overall
- 122.7 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 18, 2026.4 m
- Year built
- 2014
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 18, 2026.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
- Registered owner
- Van Oord Overig Materieel IV 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, 2026DAMEN SHIPYARD GALATI(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 |
|---|---|---|
| Call sign changed from PCHR to PCE | AIS, seen by Voydar | |
| Left IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Call sign changed from PF9939 to PCHR | 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.
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 |
|---|---|---|---|
| IJmuiden/Velsen NLIJM | Oct 31, 2026, 05:51 UTC | Oct 31, 2026, 07:03 UTC | 1 h 12 min |
| IJmuiden/Velsen NLIJM | Oct 29, 2026, 05:26 UTC | Oct 29, 2026, 15:32 UTC | 10 h 7 min |
| IJmuiden/Velsen NLIJM | Oct 27, 2026, 19:54 UTC | Oct 27, 2026, 20:54 UTC | 59 min |
| Amsterdam NLAMS | Oct 23, 2026, 05:06 UTC | Oct 27, 2026, 19:12 UTC | 4 d 14 h |
| IJmuiden/Velsen NLIJM | Oct 23, 2026, 03:11 UTC | Oct 23, 2026, 04:17 UTC | 1 h 6 min |
| IJmuiden/Velsen NLIJM | Oct 12, 2026, 17:03 UTC | Oct 12, 2026, 18:56 UTC | 1 h 53 min |
| Amsterdam NLAMS | Sep 22, 2026, 12:42 UTC | Oct 12, 2026, 17:03 UTC | 20 d 4 h |
| IJmuiden/Velsen NLIJM | Sep 16, 2026, 05:16 UTC | Sep 16, 2026, 22:07 UTC | 16 h 51 min |
| Winsum NLWNS | Sep 13, 2026, 09:55 UTC | Sep 13, 2026, 13:29 UTC | 3 h 34 min |
| Hoogkerk NLHKK | Sep 12, 2026, 11:55 UTC | Sep 13, 2026, 09:38 UTC | 21 h 43 min |
| Winsum NLWNS | Sep 12, 2026, 09:11 UTC | Sep 12, 2026, 11:55 UTC | 2 h 44 min |
| Lauwersoog NLLAN | Sep 9, 2026, 09:12 UTC | Sep 9, 2026, 14:26 UTC | 5 h 15 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 18, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 17, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 16, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 15, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 14, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 13, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 12, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 11, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 10, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 8, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 7, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 6, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 5, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 4, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 3, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 2, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 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 1, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Oct 31, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 141 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Oct 30, 2026, 00:00 UTC | IMO used twice IMO 9715505 was broadcast by two ships (MMSI 244780712 and 244820968) 182 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_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
- What kind of ship is ZK 4 ALBATROS?
- ZK 4 ALBATROS is a fishing vessel sailing under the flag of Netherlands, built in 2014 by Damen Shipyards Galați. The vessel is 122.7 m long and has a gross tonnage of 9,675.
- Who is recorded as the owner or manager of ZK 4 ALBATROS?
- Van Oord Overig Materieel IV B.V. is recorded as Registered owner for ZK 4 ALBATROS (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 ZK 4 ALBATROS?
- Voydar has no matched sanctions record displayed for ZK 4 ALBATROS 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 ZK 4 ALBATROS. 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/9715505Cite this page
ZK 4 ALBATROS. Voydar (voydar.com). https://www.voydar.com/vessel/9715505-zk-4-albatros. Retrieved November 18, 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.