Momentum Phonix
Bulk carrier · built 1995
In short
Momentum Phonix (Bulk carrier) has no AIS position on record with Voydar.
- Vessel type
- Bulk carrier
- Flag
- —
- Year built
- 1995
- Gross tonnage
- 14,430
- Size (length × beam)
- 150 m × 26 m
- Registered owner
- —
Watch this ship
Momentum Phonix 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-upIdentity & particulars
- Name
- Momentum Phonix
- IMO numberWhat is an IMO number?
- 9113874
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- Bulk carrier
- Gross tonnageGross tonnage vs deadweight
- 14,430
- Deadweight (DWT)
- Source: Wikidata, record Q117011551. Added to Voydar on September 23, 2026. Licence: CC0 1.0.23,712 t
- Length overall
- 150 m
- Beam
- 26 m
- Year built
- 1995
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 |
|---|---|---|
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from PORT OF PLAQUEMINES, LAAuthority-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 | Sep 10, 2026, 04:44 UTC | SOUTH WEST LAMMA ANCHORAGE | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Aug 14, 2026, 16:56 UTC | POTOI ISLAND | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| PORT OF PLAQUEMINES, LA | Departure | Feb 18, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF PLAQUEMINES, LA | Arrival | Feb 16, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Feb 14, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Feb 11, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Departure | Sep 17, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Arrival | Sep 13, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Jan 22, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Arrival | Jan 12, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Diego USSAN | Departure | Jan 8, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Diego USSAN | Arrival | Jan 8, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: January 29, 2002.
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 Momentum Phonix now?
- Voydar has no displayable AIS position for Momentum Phonix in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Momentum Phonix?
- Momentum Phonix is a bulk carrier, built in 1995 by Shinkurushima Toyohashi Shipbuilding. The vessel is 150 m long with a beam of 26 m and has a gross tonnage of 14,430.
- What sanctions and inspection records does Voydar hold for Momentum Phonix?
- Voydar has no matched sanctions record displayed for Momentum Phonix 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 Momentum Phonix. 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/9113874Using 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.