Skip to content

CASABLANCA A

Container ship · built 1996

IMO9106467No AIS position on record

In short

CASABLANCA A (Container ship) has no AIS position on record with Voydar.

Vessel type
Container ship
Flag
—
Year built
1996
Gross tonnage
8,633
Size (length × beam)
133 m × 23 m
Registered owner
—

Watch this ship

CASABLANCA A 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.

We email you a link and a code. That creates a free account, no password or card, and follows CASABLANCA A.

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 IMO 9106467
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

IMO numberWhat is an IMO number?
9106467
Flag
—
Vessel type
Container ship
Gross tonnageGross tonnage vs deadweight
8,633
Length overall
132.9 m
Beam
23.1 m
Year built
1996

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
ARKAS Line(not linked to a company record)
Source: Wikidata · reported · confidence 0.6 · retrieved Jun 10, 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 CharlestonAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at CharlestonAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from MiamiAuthority-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
20186,204 t1,986 t142 days262 kg
20195,086 t1,628 t138 days239 kg
20208,871 t2,840 t157 days231 kg
20216,601 t2,111 t112 days216 kg
20226,822 t2,183 t109 days232 kg
20235,755 t1,840 t92 days247 kg

Technical efficiency: EEXI (28.17 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
Charleston USCHSDepartureMay 17, 2011(date only)—USACE foreign traffic vessel entrances & clearances
Charleston USCHSArrivalApr 25, 2011(date only)—USACE foreign traffic vessel entrances & clearances
Miami USMIADepartureApr 22, 2011(date only)—USACE foreign traffic vessel entrances & clearances
Miami USMIAArrivalApr 22, 2011(date only)—USACE foreign traffic vessel entrances & clearances
Tampa USTPADepartureApr 24, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Tampa USTPAArrivalApr 2, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Miami USMIADepartureJan 16, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Miami USMIAArrivalJan 13, 2009(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureDec 23, 2008(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalDec 22, 2008(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureDec 2, 2008(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalNov 30, 2008(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: January 8, 2002.

Frequently asked questions

Where is CASABLANCA A now?
Voydar has no displayable AIS position for CASABLANCA A in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is CASABLANCA A?
CASABLANCA A is a container ship, built in 1996 by Szczecin Shipyard. The vessel is 132.9 m long with a beam of 23.1 m and has a gross tonnage of 8,633.
What sanctions and inspection records does Voydar hold for CASABLANCA A?
Voydar has no matched sanctions record displayed for CASABLANCA A 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 CASABLANCA A. 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/9106467
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