Key Sund
Tanker · Norway · built 1993 · AIS Class A
In short
Key Sund (Tanker, Norway flag) was last seen on AIS on , moored, near Zaandam (North Sea). Its crew-entered AIS destination is GBGRG>NLAMS; its reported draught is 5.1 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 11:26 UTC).
Current voyage: from IJmuiden/Velsen (departed Oct 2, 2026, 08:20 UTC) to GBGRG>NLAMS
- Vessel type
- Tanker
- Flag
- Norway
- Year built
- 1993
- Gross tonnage
- 3,206
- Size (length × beam)
- 96 m
- Registered owner
- —
Watch this ship
Get an email when Key Sund 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 Key Sund.
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
- 52.4242° N, 4.7487° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 60°
- Heading
- 347°
Last 30 days: 5 port calls (IJmuiden/Velsen, Grangemouth, Pernis, Averoy, and Kristiansund).
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
- Key Sund
- IMO numberWhat is an IMO number?
- 8920567
- MMSIWhat is an MMSI?
- 259360000
- Call signWhat is a call sign?
- LIFL3
- Flag
- Norway
- Vessel type
- Tanker
- AIS ship type
- Tanker (hazardous cat. B)
- Gross tonnageGross tonnage vs deadweight
- 3,206
- Length overall
- 96.4 m
- Beam
- —
- Year built
- 1993
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.
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 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 |
|---|---|---|
| Left IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left GrangemouthAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at GrangemouthAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left PernisAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at PernisAIS-detected | Voydar port-call detector (AIS geofence) | |
| Port State Control inspection at MASSENA, New York | USCG PSIX / CGMIX inspections | |
| Inspection at WASHINGTON, District of Columbia | USCG PSIX / CGMIX inspections | |
| Reported departure from DULUTH-SUPERIOR HARBOR, MN AND WIAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Port State Control inspection at Duluth, Minnesota | USCG PSIX / CGMIX inspections | |
| Reported arrival at DULUTH-SUPERIOR HARBOR, MN AND WIAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Port State Control inspection at MASSENA, New York | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Duluth, Minnesota | USCG PSIX / CGMIX inspections |
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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Aug 10, 2015 | Vessel InspectionPSC | MASSENA, New York | clean |
| Dec 24, 2008 | Vessel Inspection | WASHINGTON, District of Columbia | clean |
| Jul 29, 2004 | Vessel InspectionPSC | Duluth, Minnesota | clean |
| Jul 24, 2004 | Vessel InspectionPSC | MASSENA, New York | clean |
| Jul 21, 2004 | Vessel InspectionPSC | Duluth, Minnesota | clean |
Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.
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 2, 2026, 07:35 UTC | Oct 2, 2026, 08:20 UTC | 45 min |
| Grangemouth GBGRG | Sep 28, 2026, 21:45 UTC | Sep 29, 2026, 18:46 UTC | 21 h 1 min |
| Pernis NLPER | Sep 20, 2026, 22:55 UTC | Sep 22, 2026, 06:07 UTC | 31 h 12 min |
| Averoy NOAVE | Sep 13, 2026, 10:58 UTC | Sep 14, 2026, 13:13 UTC | 26 h 15 min |
| Kristiansund NOKSU | Sep 13, 2026, 08:34 UTC | Sep 13, 2026, 10:58 UTC | 2 h 24 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 |
|---|---|---|---|---|
| DULUTH-SUPERIOR HARBOR, MN AND WI | Departure | Jul 30, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
| DULUTH-SUPERIOR HARBOR, MN AND WI | Arrival | Jul 29, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: July 29, 2004.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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.
Predicted arrival
Voydar estimates arrival at Amsterdam around Oct 5, 2026, 10:23 UTC, most likely between Oct 2, 2026, 16:23 UTC and Oct 19, 2026, 11:20 UTC. Based on 71 past transits between NLIJM and Amsterdam seen in our port calls. The crew-reported ETA is Oct 1, 2026, 07:00 UTC.
Medium (56%) · Method seadar.behaviour.eta_prediction v1
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 Key Sund now?
- Key Sund (Tanker, Norway flag) was last seen on AIS on Oct 2, 2026, 12:06 UTC, moored, near Zaandam (North Sea). The crew-entered destination was GBGRG>NLAMS (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 11:26 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Key Sund?
- Key Sund is a tanker sailing under the flag of Norway, built in 1993 by Aarhus Flydedok. The vessel is 96.4 m long and has a gross tonnage of 3,206.
- What sanctions and inspection records does Voydar hold for Key Sund?
- Voydar has no matched sanctions record displayed for Key Sund 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. Key Sund has 5 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
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/8920567Using 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.