Refined
Bulk carrier · built 1996
In short
Refined (Bulk carrier) has no AIS position on record with Voydar.
- Vessel type
- Bulk carrier
- Flag
- —
- Year built
- 1996
- Gross tonnage
- 18,070
- Size (length × beam)
- 175 m × 26 m
- Registered owner
- —
Watch this ship
Get an email when Refined 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 Refined.
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
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-upIdentity & particulars
- Name
- Refined
- IMO numberWhat is an IMO number?
- 9153707
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- Bulk carrier
- Gross tonnageGross tonnage vs deadweight
- 18,070
- Deadweight (DWT)
- Source: Wikidata, record Q117018355. Added to Voydar on September 23, 2026. Licence: CC0 1.0.28,587 t
- Length overall
- 175 m
- Beam
- 26 m
- Year built
- 1996
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 Corpus ChristiAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at Corpus ChristiAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| 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.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 3,887 t | 1,241 t | 70 days | 235 kg |
| 2019 | 4,696 t | 1,500 t | 76 days | 286 kg |
Technical efficiency: EIV (6.31 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Corpus Christi USCRP | Departure | Oct 17, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Arrival | Oct 14, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF PLAQUEMINES, LA | Departure | Sep 14, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Arrival | Aug 23, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Mar 26, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Mar 23, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Mar 12, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Mar 10, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Feb 5, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Jan 11, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Departure | Dec 18, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Arrival | Dec 15, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: March 4, 2002.
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 Refined now?
- Voydar has no displayable AIS position for Refined in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Refined?
- Refined is a bulk carrier, built in 1996 by Hudong-Zhonghua Shipbuilding. The vessel is 175 m long with a beam of 26 m and has a gross tonnage of 18,070.
- What sanctions and inspection records does Voydar hold for Refined?
- Voydar has no matched sanctions record displayed for Refined 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 Refined. 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/9153707Using 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.