Skip to content

Annaba

Container ship · Portugal · built 2006 · AIS Class A

IMO9306201MMSI255806514Call signCQEX7Last AIS position Oct 2, 2026, 23:38 UTC

In short

Annaba (Container ship, Portugal flag) was last seen on AIS on , moored, in the port of Hamburg. Its crew-entered AIS destination is DEHAM (Hamburg); its reported draught is 9.4 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 23:23 UTC). It arrived there on Oct 1, 2026, 20:30 UTC. ISM manager: Peter Dohle Schiffahrts-KG (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Container ship
Year built
2006
Gross tonnage
15,487
Size (length × beam)
158 m × 26 m

Watch this ship

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

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 ANNABA
Photo: Wolfgang Fricke · Licence: CC BY 3.0 · via Wikimedia Commons

Last reported position

received
Position
53.531° N, 9.9113° E
Area
North Sea
Speed
0 kn
Course
219°
Heading
304°
53.531° N, 9.9113° E
Open the full live map →

Last 30 days: 9 port calls (Hamburg, Bremerhaven, Brunsbuttel, Holtenau, Karskar, Gdynia, Kiel, Kiel Canal, and Altenwerder).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls 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
Annaba
IMO numberWhat is an IMO number?
9306201
MMSIWhat is an MMSI?
255806514
Call signWhat is a call sign?
CQEX7
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
15,487
Length overall
158.3 m
Beam
25.7 m
Year built
2006

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.

Operator
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · 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
Arrived at HamburgAIS-detectedVoydar port-call detector (AIS geofence)
Left BremerhavenAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BremerhavenAIS-detectedVoydar port-call detector (AIS geofence)
Left BrunsbuttelAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BrunsbuttelAIS-detectedVoydar port-call detector (AIS geofence)
Reported arrival at GdyniaAuthority-reportedUrząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk)

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
201816,230 t5,210 t261 days222 kg
201912,697 t4,075 t254 days227 kg
202013,644 t4,358 t222 days253 kg
202114,405 t4,597 t212 days261 kg
202213,627 t4,330 t177 days280 kg
20237,601 t2,426 t97 days295 kg
202410,144 t3,250 t147 days279 kg
202510,311 t3,328 t147 days284 kg

Technical efficiency: EEXI (18.9 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.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Hamburg DEHAMOct 1, 2026, 20:30 UTCin port—
Bremerhaven DEBRVSep 30, 2026, 20:38 UTCOct 1, 2026, 09:05 UTC12 h 27 min
Brunsbuttel DEBRBSep 30, 2026, 13:44 UTCSep 30, 2026, 15:07 UTC1 h 22 min
Holtenau DEHTUSep 30, 2026, 03:37 UTCSep 30, 2026, 05:00 UTC1 h 23 min
Karskar SEKASSep 27, 2026, 11:40 UTCSep 28, 2026, 13:21 UTC25 h 41 min
Gdynia PLGDYSep 25, 2026, 15:20 UTCSep 26, 2026, 08:17 UTC16 h 56 min
Kiel DEKELSep 23, 2026, 16:46 UTCSep 23, 2026, 17:39 UTC53 min
Kiel Canal DECKLSep 23, 2026, 06:54 UTCSep 23, 2026, 11:14 UTC4 h 20 min
Altenwerder DEHHVSep 20, 2026, 15:41 UTCSep 21, 2026, 04:44 UTC13 h 2 min

Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Gdynia PLGDYArrivalSep 25, 2026, 15:44 UTCBu garskieUrząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk)

Records published by the authority named on each row. Earliest record for this ship: September 25, 2026.

Behaviour at sea Voydar-derived

Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.

WhenWhat we observedConfidence
Oct 2, 2026, 11:35 UTC
Draught change

Reported draught went from 9.9 m to 9.4 m while in port at Hamburg. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 28, 2026, 14:06 UTC
Draught change

Reported draught went from 8.6 m to 9.4 m after leaving Karskar. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)

Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.

Source: Fintraffic / digitraffic.fi, license CC 4.0 BY. Licence: CC BY 4.0.

Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.

How these are computed →

Frequently asked questions

Where is Annaba now?
Annaba (Container ship, Portugal flag) was last seen on AIS on Oct 2, 2026, 23:38 UTC, moored, in the port of Hamburg. The crew-entered destination was DEHAM (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 23:23 UTC). This report does not confirm the ship’s current route.
What kind of ship is Annaba?
Annaba is a container ship sailing under the flag of Portugal, built in 2006 by Jiangsu Yangzijiang Shipbuilding. The vessel is 158.3 m long with a beam of 25.7 m and has a gross tonnage of 15,487.
Who is recorded as the owner or manager of Annaba?
Peter Dohle Schiffahrts-KG is recorded as ISM manager for Annaba (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 Annaba?
Voydar has no matched sanctions record displayed for Annaba 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 Annaba. 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/9306201
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