Skip to content

Valle di Cordoba

Oil tanker · built 2005

IMO9295311No AIS position on record

In short

Valle di Cordoba (Oil tanker) has no AIS position on record with Voydar.

Vessel type
Oil tanker
Flag
—
Year built
2005
Gross tonnage
25,063
Size (length × beam)
176 m
Registered owner
—

Watch this ship

Valle di Cordoba 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.

Photo of Valle di Cordoba
Photo: Alf van Beem · Licence: CC0 · 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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
Valle di Cordoba
IMO numberWhat is an IMO number?
9295311
Flag
—
Gross tonnageGross tonnage vs deadweight
25,063
Length overall
176 m
Beam
—
Year built
2005

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 year 2025 · reported · confidence 0.9 · retrieved Oct 5, 2026
Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Oct 5, 2026
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
ISM manager: Dynaverse Limited (previously Navigazione Montanari SpA)Voydar relationship-change derivation (derived by Voydar from EU MRV (THETIS-MRV) emissions)
Reported departure from New YorkAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at New YorkAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)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
201812,875 t4,109 t111 days487 kg
201914,110 t4,502 t231 days391 kg
202013,267 t4,197 t309 days365 kg
202113,277 t4,198 t181 days349 kg
202214,683 t4,640 t232 days373 kg
202312,702 t4,010 t144 days346 kg
202413,071 t4,121 t115 days392 kg
20257,512 t2,358 t101 days398 kg

Technical efficiency: EIV (7.8 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
New York USNYCDepartureMay 24, 2011(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalMay 23, 2011(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureJul 21, 2010(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalJul 21, 2010(date only)—USACE foreign traffic vessel entrances & clearances
NORTHVILLE, L.I., NYDepartureJul 10, 2010(date only)—USACE foreign traffic vessel entrances & clearances
NORTHVILLE, L.I., NYArrivalJul 10, 2010(date only)—USACE foreign traffic vessel entrances & clearances
New Haven USHVNDepartureJul 9, 2010(date only)—USACE foreign traffic vessel entrances & clearances
New Haven USHVNArrivalJul 8, 2010(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureJun 6, 2008(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LAArrivalJun 1, 2008(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureMay 24, 2008(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalMay 24, 2008(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is Valle di Cordoba now?
Voydar has no displayable AIS position for Valle di Cordoba in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Valle di Cordoba?
Valle di Cordoba is an oil tanker, built in 2005 by HD Hyundai Mipo. The vessel is 176 m long and has a gross tonnage of 25,063.
What sanctions and inspection records does Voydar hold for Valle di Cordoba?
Voydar has no matched sanctions record displayed for Valle di Cordoba 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 Valle di Cordoba. 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/9295311
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