Skip to content

IMO 8916748

Reefer ship · built 1990

IMO8916748No AIS position on record

In short

IMO 8916748 (Reefer ship) has no AIS position on record with Voydar.

Vessel type
Reefer ship
Flag
—
Year built
1990
Gross tonnage
8,483
Size (length × beam)
141 m × 21 m
Registered owner
—

Watch this ship

Get an email when IMO 8916748 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 IMO 8916748.

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 IMO 8916748
Photo: Pjotr Mahhonin · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

No AIS position on record for this vessel. Identity and particulars are 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
IMO 8916748
IMO numberWhat is an IMO number?
8916748
Flag
—
Vessel type
Reefer ship
Gross tonnageGross tonnage vs deadweight
8,483
Length overall
141 m
Beam
20.6 m
Year built
1990

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.

DateEventSource
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)
Former name: Zefyros ReeferWikidata
Reported departure from BELLINGHAM BAY AND HARBOR, WAAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at BELLINGHAM BAY AND HARBOR, WAAuthority-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.

Former and other names

Names attested for this ship other than its current name.

NameEvidenceDateSource
Zefyros ReeferFormer nameJan 1, 2016Wikidata

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.

Source: Wikidata. Licence: CC0 1.0.

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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Hong Kong HKHKGArrivalNov 30, 2018, 15:25 UTCSWLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
BELLINGHAM BAY AND HARBOR, WADepartureJun 13, 2015(date only)—USACE foreign traffic vessel entrances & clearances
BELLINGHAM BAY AND HARBOR, WAArrivalMay 25, 2015(date only)—USACE foreign traffic vessel entrances & clearances
UNALASKA ISLAND, ALASKA (INCLUDING DUTCH & ILIULIUK HARBORS)DepartureMay 20, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Ponce PRPSEArrivalMay 17, 2015(date only)—USACE foreign traffic vessel entrances & clearances
JACKSONVILLE HARBOR, FLDepartureSep 20, 2013(date only)—USACE foreign traffic vessel entrances & clearances
JACKSONVILLE HARBOR, FLArrivalSep 17, 2013(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYDepartureSep 13, 2013(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalSep 9, 2013(date only)—USACE foreign traffic vessel entrances & clearances
DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIADepartureApr 2, 2010(date only)—USACE foreign traffic vessel entrances & clearances
DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIAArrivalApr 2, 2010(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBDepartureApr 2, 2009(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: March 20, 2002.

Frequently asked questions

Where is IMO 8916748 now?
Voydar has no displayable AIS position for IMO 8916748 in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is IMO 8916748?
IMO 8916748 is a reefer ship, built in 1990 by Sasebo Heavy Industries. The vessel is 141 m long with a beam of 20.6 m and has a gross tonnage of 8,483.
What sanctions and inspection records does Voydar hold for IMO 8916748?
Voydar has no matched sanctions record displayed for IMO 8916748 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 IMO 8916748. 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/8916748
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