Where is Power D now?

Voydar has no displayable AIS position for Power D in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.

What kind of ship is Power D?

Power D is a ship, built in 2003. The vessel is 332.9 m long with a beam of 60 m and has a gross tonnage of 161,306.

What sanctions and inspection records does Voydar hold for Power D?

Voydar has no matched sanctions record displayed for Power D 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 Power D. Missing records do not establish whether the ship has been detained.

Power D

ship · built 2003

IMO9241102No AIS position on record

Open in Terminal

In short

Power D (ship) has no AIS position on record with Voydar.

Vessel type: ship
Flag: —
Year built: 2003
Gross tonnage: 161,306
Size (length × beam): 333 m × 60 m
Registered owner: —

Watch this ship

Power D has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.

Free forever. No card. A free account follows up to 5 ships and ports.

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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name: Power D
IMO numberWhat is an IMO number?: 9241102
MMSIWhat is an MMSI?: —
Call signWhat is a call sign?: —
Flag: —
Vessel type: ship
Gross tonnageGross tonnage vs deadweight: 161,306
Deadweight (DWT): Source: Wikidata, record Q84264366. Added to Voydar on September 23, 2026. Licence: CC0 1.0.319,012 t
Length overall: 332.9 m
Beam: 60 m
Year built: 2003

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.

Date	Event	Source
Oct 5, 2026, 16:58 UTC	Reported arrival at Hong KongAuthority-reported	Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
May 10, 2016	Reported departure from Long BeachAuthority-reported	USACE foreign traffic vessel entrances & clearances
May 6, 2016	Reported arrival at Long BeachAuthority-reported	USACE 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.

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

Port	Record	Date (UTC)	Berth	Source
Hong Kong HKHKG	Arrival	Oct 5, 2026, 16:58 UTC	SOUTH LAMMA DG ANCHORAGE	Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Long Beach USLGB	Departure	May 10, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Long Beach USLGB	Arrival	May 6, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Long Beach USLGB	Departure	Apr 24, 2012(date only)	—	USACE foreign traffic vessel entrances & clearances
Long Beach USLGB	Arrival	Apr 22, 2012(date only)	—	USACE foreign traffic vessel entrances & clearances
Long Beach USLGB	Departure	Aug 7, 2004(date only)	—	USACE foreign traffic vessel entrances & clearances
Los Angeles USLAX	Arrival	Aug 1, 2004(date only)	—	USACE foreign traffic vessel entrances & clearances
Long Beach USLGB	Departure	Apr 4, 2003(date only)	—	USACE foreign traffic vessel entrances & clearances
Long Beach USLGB	Arrival	Apr 3, 2003(date only)	—	USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: April 3, 2003.

Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.

Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.

Frequently asked questions

Where is Power D now?: Voydar has no displayable AIS position for Power D in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Power D?: Power D is a ship, built in 2003. The vessel is 332.9 m long with a beam of 60 m and has a gross tonnage of 161,306.
What sanctions and inspection records does Voydar hold for Power D?: Voydar has no matched sanctions record displayed for Power D 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 Power D. 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/9241102

View JSON API documentationFree without a key for occasional use; use an API key for more.

Follow by RSS Open data

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