Skip to content

Indra Oldendorff

Bulk carrier · built 2016

IMO9722338No AIS position on record

In short

Indra Oldendorff (Bulk carrier) has no AIS position on record with Voydar. ISM manager: Connaught Shipmanagement (HK) Limited (source: EU MRV (THETIS-MRV) emissions, reporting year 2024).

Vessel type
Bulk carrier
Flag
—
Year built
2016
Gross tonnage
36,294
Size (length × beam)
200 m

Watch this ship

Get an email when Indra Oldendorff 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 Indra Oldendorff.

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.

Photo of Indra Oldendorff
Photo: Farid mernissi · Licence: CC BY-SA 4.0 · 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)

Try the live demo, no sign-up

Identity & particulars

Name
Indra Oldendorff
IMO numberWhat is an IMO number?
9722338
Flag
—
Gross tonnageGross tonnage vs deadweight
36,294
Length overall
199.9 m
Beam
—
Year built
2016

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 2024 · reported · confidence 0.9 · retrieved Sep 28, 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 Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from Corpus ChristiAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at Corpus ChristiAuthority-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
20192,047 t652 t36 days266 kg
20202,274 t728 t38 days226 kg
20214,133 t1,307 t44 days308 kg
20222,007 t633 t25 days262 kg
20236,699 t2,140 t86 days304 kg
20240 t0 t0 days—

Technical efficiency: EEDI (3.87 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
Hong Kong HKHKGArrivalDec 22, 2023, 23:57 UTCPOTOI ISLANDHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Corpus Christi USCRPDepartureOct 30, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPArrivalOct 28, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LADepartureOct 24, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LAArrivalOct 22, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureJul 29, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPArrivalJul 27, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Vancouver USVANDepartureApr 29, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Astoria USASTArrivalApr 27, 2016(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: April 27, 2016.

Frequently asked questions

Where is Indra Oldendorff now?
Voydar has no displayable AIS position for Indra Oldendorff in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Indra Oldendorff?
Indra Oldendorff is a bulk carrier, built in 2016 by Jiangsu Yangzijiang Shipbuilding. The vessel is 199.9 m long and has a gross tonnage of 36,294.
Who is recorded as the owner or manager of Indra Oldendorff?
Connaught Shipmanagement (HK) Limited is recorded as ISM manager for Indra Oldendorff (source: EU MRV (THETIS-MRV) emissions; reporting year 2024). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for Indra Oldendorff?
Voydar has no matched sanctions record displayed for Indra Oldendorff 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 Indra Oldendorff. 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/9722338
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