Skip to content

African Eagle

Bulk carrier · built 2003

IMO9257046No AIS position on record

In short

African Eagle (Bulk carrier) has no AIS position on record with Seadar. ISM manager: Dockendale Ship Management FZCO (source: EU MRV (THETIS-MRV) emissions, reporting year 2024).

Vessel type
Bulk carrier
Flag
—
Year built
2003
Gross tonnage
17,944
Size (length × beam)
178 m × 26 m

Watch this ship

Get an email when African Eagle 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 African Eagle.

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
African Eagle
IMO numberWhat is an IMO number?
9257046
Flag
—
Vessel type
Bulk carrier
Gross tonnageGross tonnage vs deadweight
17,944
Length overall
178 m
Beam
26 m
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 year 2024 · reported · confidence 0.9 · retrieved Sep 28, 2026

Timeline

Dated events for this ship from every source Seadar holds, newest first. Each line names its source; derived items say how they were derived.

DateEventSource
Reported departure from BeaumontAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at BeaumontAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from GalvestonAuthority-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,373 t758 t36 days221 kg
20201,356 t430 t21 days201 kg
20224,863 t1,539 t79 days245 kg
20242,613 t823 t34 days260 kg

Technical efficiency: EIV (8.55 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 Seadar 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
Beaumont USBPTDepartureOct 15, 2007(date only)—USACE foreign traffic vessel entrances & clearances
Beaumont USBPTArrivalOct 14, 2007(date only)—USACE foreign traffic vessel entrances & clearances
Galveston USGLSDepartureSep 1, 2007(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalAug 29, 2007(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureAug 25, 2007(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalAug 24, 2007(date only)—USACE foreign traffic vessel entrances & clearances
Vancouver USVANDepartureJan 25, 2007(date only)—USACE foreign traffic vessel entrances & clearances
Vancouver USVANArrivalJan 19, 2007(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureJan 14, 2007(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalJan 14, 2007(date only)—USACE foreign traffic vessel entrances & clearances
Portland USPDXDepartureSep 22, 2006(date only)—USACE foreign traffic vessel entrances & clearances
Vancouver USVANArrivalSep 17, 2006(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is African Eagle now?
Seadar has no displayable AIS position for African Eagle in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is African Eagle?
African Eagle is a bulk carrier, built in 2003. The vessel is 178 m long with a beam of 26 m and has a gross tonnage of 17,944.
Who is recorded as the owner or manager of African Eagle?
Dockendale Ship Management FZCO is recorded as ISM manager for African Eagle (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 Seadar hold for African Eagle?
Seadar has no matched sanctions record displayed for African Eagle from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for African Eagle. 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/9257046
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