Skip to content

Clipper Valour

Bulk carrier · built 2003

IMO9285407No AIS position on record

In short

Clipper Valour (Bulk carrier) has no AIS position on record with Voydar. ISM manager: Beyaz Denizcilik Ltd Sti (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Bulk carrier
Flag
—
Year built
2003
Gross tonnage
22,072
Size (length × beam)
179 m

Watch this ship

Get an email when Clipper Valour 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 Clipper Valour.

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

Identity & particulars

Name
Clipper Valour
IMO numberWhat is an IMO number?
9285407
Flag
—
Gross tonnageGross tonnage vs deadweight
22,072
Length overall
179.3 m
Beam
—
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.

ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 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 GalvestonAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at GalvestonAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from PORT OF SOUTH LOUISIANA (LA)Authority-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
2018606 t194 t13 days229 kg
20191,683 t535 t62 days268 kg
20202,499 t798 t39 days244 kg
20217,215 t2,308 t110 days241 kg
20225,107 t1,631 t86 days212 kg
20231,652 t526 t29 days208 kg
20241,710 t545 t30 days204 kg
20253,935 t1,251 t71 days207 kg

Technical efficiency: EEXI (6.25 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

PortRecordDate (UTC)BerthSource
Galveston USGLSDepartureAug 11, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Galveston USGLSArrivalJul 31, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureJul 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalJul 14, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYDepartureJun 7, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)ArrivalMay 23, 2016(date only)—USACE foreign traffic vessel entrances & clearances
ELIZABETH RIVER (SOUTHERN BRANCH) VADepartureJan 11, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF HOPEWELL, VA (INCLUDED IN JAMES RIVER VA CONSOLIDATED REPORT)ArrivalJan 4, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Tampa USTPADepartureApr 10, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Tampa USTPAArrivalApr 10, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Galveston USGLSDepartureApr 7, 2015(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalApr 3, 2015(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: February 5, 2004.

Frequently asked questions

Where is Clipper Valour now?
Voydar has no displayable AIS position for Clipper Valour in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Clipper Valour?
Clipper Valour is a bulk carrier, built in 2003. The vessel is 179.3 m long and has a gross tonnage of 22,072.
Who is recorded as the owner or manager of Clipper Valour?
Beyaz Denizcilik Ltd Sti is recorded as ISM manager for Clipper Valour (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for Clipper Valour?
Voydar has no matched sanctions record displayed for Clipper Valour 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 Clipper Valour. 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/9285407
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