Skip to content

Rich Breeze

Oil tanker · built 2009

IMO9380051No AIS position on record

In short

Rich Breeze (Oil tanker) has no AIS position on record with Voydar. ISM manager: Cymare Navigation FZC (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Oil tanker
Flag
—
Year built
2009
Gross tonnage
26,900
Size (length × beam)
183 m × 32 m

Watch this ship

Rich Breeze 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
Rich Breeze
IMO numberWhat is an IMO number?
9380051
Flag
—
Gross tonnageGross tonnage vs deadweight
26,900
Length overall
183 m
Beam
32.2 m
Year built
2009

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 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
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 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
20188,799 t2,769 t100 days303 kg
20231,700 t539 t18 days408 kg
20241,857 t588 t33 days281 kg
20251,397 t440 t18 days263 kg

Technical efficiency: EEXI (5.1 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 USNYCDepartureDec 31, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalDec 29, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureNov 12, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)ArrivalNov 11, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Baton Rouge USBTRDepartureSep 26, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Baton Rouge USBTRArrivalSep 25, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureJun 20, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalJun 18, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCDepartureJun 4, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalJun 3, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureApr 29, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)ArrivalApr 29, 2016(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: May 13, 2009.

Frequently asked questions

Where is Rich Breeze now?
Voydar has no displayable AIS position for Rich Breeze in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Rich Breeze?
Rich Breeze is an oil tanker, built in 2009 by Onomichi Dockyard. The vessel is 183 m long with a beam of 32.2 m and has a gross tonnage of 26,900.
Who is recorded as the owner or manager of Rich Breeze?
Cymare Navigation FZC is recorded as ISM manager for Rich Breeze (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 Rich Breeze?
Voydar has no matched sanctions record displayed for Rich Breeze 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 Rich Breeze. 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/9380051
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