Skip to content

Olympia Ocean Carriers Ltd

Olympia Ocean Carriers Ltd is linked to 6 vessels in public records, grouped below by role. Each link shows its source, date and confidence.

Fleet by role

Vessels under ISM management 6

The company responsible for the ship's safety management (ISM) as declared in its EU MRV emissions report, per reporting year.

Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Oct 5, 2026

VesselTypeFlagGTBuiltPeriodStatus
ONE ENERGYIMO 9592123CargoCyprus44,3232011reporting years 2024–2025Latest report
ONE OCEANIMO 9460904CargoCyprus43,2002009reporting year 2025Latest report
CAPE SUNIMO 9953573CargoCyprus——reporting years 2024–2025Latest report
CAPE BREEZEIMO 9518919CargoCyprus93,9602010reporting year 2024Latest report
CAPE VENTUREIMO 9518921CargoCyprus93,9602010reporting year 2024Latest report
ARETHOUSAIMO 9618020CargoCyprus40,3342012reporting year 2024Latest report

Company facts

Legal name
OLYMPIA OCEAN CARRIERS LTD
Legal form (ELF code)
Limited Liability Company
Jurisdiction
Cyprus
Legal address
Limassol, Cyprus
Headquarters
Limassol, Cyprus
Entity status
ACTIVE
LEI registration status
LAPSED

Source: GLEIF LEI records (Level 1 reference data + Level 2 parent relationships) · reported

Identifiers

  • IMO company number5781402Source: EU MRV (THETIS-MRV) emissions
  • LEI894500N027JNAZJNV089Source: GLEIF LEI records (Level 1 reference data + Level 2 parent relationships)
  • National registerRA000162:HE277542Source: GLEIF LEI records (Level 1 reference data + Level 2 parent relationships)

Sources on this page

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/companies/411111
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