Skip to content

Aegean Spire

General cargo ship · built 2008

IMO9370381No AIS position on record

In short

Aegean Spire (General cargo ship) has no AIS position on record with Voydar.

Flag
—
Year built
2008
Gross tonnage
21,211
Size (length × beam)
180 m × 28 m
Registered owner
—

Watch this ship

Aegean Spire 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 Aegean Spire
Photo: Farid mernissi · Licence: CC BY 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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
Aegean Spire
IMO numberWhat is an IMO number?
9370381
Flag
—
Gross tonnageGross tonnage vs deadweight
21,211
Length overall
179.9 m
Beam
28.2 m
Year built
2008

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

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)
ISM manager: DALIAN CHUN AN SHIP MANAGEMENT CO., LTD. (previously SEASPIRE MARITIME INC.)Voydar relationship-change derivation (derived by Voydar from EU MRV (THETIS-MRV) emissions)
Reported departure from PortlandAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at PORT OF KALAMA, WAAuthority-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
20195,616 t1,791 t93 days239 kg
20203,789 t1,210 t61 days245 kg
20216,095 t1,943 t96 days234 kg
20223,992 t1,269 t62 days273 kg
20232,127 t679 t33 days243 kg
20244,642 t1,477 t80 days246 kg
20252,419 t770 t45 days217 kg

Technical efficiency: EEXI (6.11 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 HKHKGArrivalSep 22, 2026, 09:36 UTCSWLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Portland USPDXDepartureAug 12, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF KALAMA, WAArrivalAug 8, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF KALAMA, WADepartureJun 8, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Astoria USASTArrivalJun 6, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureDec 26, 2015(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalDec 19, 2015(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYDepartureDec 10, 2015(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalDec 9, 2015(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureJun 23, 2015(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalJun 18, 2015(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureJun 10, 2015(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: October 6, 2008.

Frequently asked questions

Where is Aegean Spire now?
Voydar has no displayable AIS position for Aegean Spire in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Aegean Spire?
Aegean Spire is a general cargo ship, built in 2008. The vessel is 179.9 m long with a beam of 28.2 m and has a gross tonnage of 21,211.
What sanctions and inspection records does Voydar hold for Aegean Spire?
Voydar has no matched sanctions record displayed for Aegean Spire 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 Aegean Spire. 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/9370381
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