Skip to content

DISKO ISLAND

Bulk carrier · Singapore · built 2012 · AIS Class A

IMO9520596MMSI563301400Call sign9V8869Last AIS position Sep 30, 2026, 08:17 UTC

In short

DISKO ISLAND (Bulk carrier, Singapore flag) was last seen on AIS on , under way at 11.3 kn, near Norfolk (North Atlantic Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is FRDKK (Dunkerque), with an ETA of Oct 13, 2026, 10:00 UTC; its reported draught is 12.3 m (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 07:42 UTC).

Current voyage: from Newport News (departed Sep 30, 2026, 07:00 UTC) to FRDKK (Dunkerque)

Vessel type
Bulk carrier
Year built
2012
Gross tonnage
32,309
Size (length × beam)
—
Registered owner
—

Watch this ship

Get an email when DISKO ISLAND 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 DISKO ISLAND.

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.

Photo of DISKO ISLAND
Photo: Alf van Beem · Licence: Public domain · via Wikimedia Commons

Last reported position

received
Position
36.9643° N, 76.0749° W
Area
North Atlantic Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
11.3 kn
Course
108°
Heading
107°
36.9643° N, 76.0749° W
Open the full live map →

Last 30 days: 1 port call (Newport News).

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-up

Identity & particulars

Name
DISKO ISLAND
IMO numberWhat is an IMO number?
9520596
MMSIWhat is an MMSI?
563301400
Call signWhat is a call sign?
9V8869
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
32,309
Length overall
—
Beam
—
Year built
2012

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.

No owner, operator or manager is recorded for this vessel yet.

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.

DateEventSource
Left Newport NewsAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Newport NewsAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from Long BeachAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at Long BeachAuthority-reportedUSACE foreign traffic vessel entrances & clearances

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.

Emissions & fuel consumption

Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
2018386 t124 t3 days315 kg
20197,228 t2,311 t78 days312 kg
20208,937 t2,824 t118 days292 kg
20213,241 t1,027 t36 days302 kg

Technical efficiency: EIV (5.76 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.

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

PortArrivedDepartedTime in port
Newport News USNNSSep 28, 2026, 21:52 UTCSep 30, 2026, 07:00 UTC33 h 8 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

PortRecordDate (UTC)BerthSource
Hong Kong HKHKGArrivalAug 10, 2025, 11:38 UTCSWLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Long Beach USLGBDepartureDec 27, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBArrivalDec 26, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Portland USPDXDepartureSep 15, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Portland USPDXArrivalSep 7, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Tacoma USTIWDepartureJan 31, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Tacoma USTIWArrivalJan 31, 2014(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureNov 5, 2013(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)ArrivalNov 4, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Beaumont USBPTDepartureNov 1, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Beaumont USBPTArrivalOct 28, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureOct 24, 2013(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: October 14, 2013.

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.

WhenWhat we observedConfidence
Sep 30, 2026, 07:42 UTC
Draught change

Reported draught went from 7.7 m to 12.3 m after leaving Newport News. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)

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.

How these are computed →

Frequently asked questions

Where is DISKO ISLAND now?
DISKO ISLAND (Bulk carrier, Singapore flag) was last seen on AIS on Sep 30, 2026, 08:17 UTC, under way at 11.3 kn, near Norfolk (North Atlantic Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was FRDKK (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 07:42 UTC). This report does not confirm the ship’s current route.
What kind of ship is DISKO ISLAND?
DISKO ISLAND is a bulk carrier sailing under the flag of Singapore, built in 2012. The vessel has a gross tonnage of 32,309.
What sanctions and inspection records does Voydar hold for DISKO ISLAND?
Voydar has no matched sanctions record displayed for DISKO ISLAND 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 DISKO ISLAND. Missing records do not establish whether the ship has been detained.

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/9520596
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using 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.

See plans