Where is Cape Brindisi now?

Voydar has no displayable AIS position for Cape Brindisi in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.

What kind of ship is Cape Brindisi?

Cape Brindisi is an oil tanker, built in 2005 by HD Hyundai Heavy Industries. The vessel is 274 m long and has a gross tonnage of 81,076.

What sanctions and inspection records does Voydar hold for Cape Brindisi?

Cape Brindisi appears on the OFAC SDN list under SDGT. No matched inspection records are displayed for Cape Brindisi. Missing records do not establish whether the ship has been detained.

Sanctioned vessel

Cape Brindisi appears on the OFAC SDN list under SDGT. Verify at OFAC.

Every vessel on:OFAC SDN list

Cape Brindisi

Oil tanker · built 2005

IMO9293143No AIS position on record

Open in Terminal

In short

Cape Brindisi (Oil tanker) has no AIS position on record with Voydar. It appears on a sanctions list (details below).

Vessel type: Oil tanker
Flag: —
Year built: 2005
Gross tonnage: 81,076
Size (length × beam): 274 m
Registered owner: —

Watch this ship

Cape Brindisi 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 Cape Brindisi.

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: Cape Brindisi
IMO numberWhat is an IMO number?: 9293143
MMSIWhat is an MMSI?: —
Call signWhat is a call sign?: —
Flag: —
Vessel type: Detailed type from EU MRV (THETIS-MRV) emissionsOil tanker
Gross tonnageGross tonnage vs deadweight: 81,076
Length overall: 274 m
Beam: —
Year built: 2005

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: COLUMBIA Shipmanagement (Deutschland) GmbH
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
Columbia Shipmanagement(not linked to a company record)
Source: Wikidata · reported · confidence 0.6 · retrieved Jun 10, 2026
Builder: HD Hyundai Heavy Industries
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.

Date	Event	Source
Jul 22, 2020, 19:28 UTC	Reported departure from Hong KongAuthority-reported	Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Jul 21, 2020, 12:23 UTC	Reported arrival at Hong KongAuthority-reported	Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Aug 2, 2015	Reported departure from PORT OF SOUTH LOUISIANA (LA)Authority-reported	USACE foreign traffic vessel entrances & clearances
Jul 31, 2015	Reported arrival at PORT OF SOUTH LOUISIANA (LA)Authority-reported	USACE 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.

Former and other names

Names attested for this ship other than its current name.

Name	Evidence	Date	Source
KASPER	Name on a sanctions list	—	OFAC Specially Designated Nationals list

A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.

Source: OFAC Specially Designated Nationals list. Licence: US Government public domain (17 U.S.C. §105).

Sanctions listings

Every listing of this ship on the sanctions lists Voydar tracks, current and past.

List	Programme	Listed as	Listed	Status
OFAC SDN list (US)	SDGT	KASPER	not published by the list	In force

Source: OFAC Specially Designated Nationals list. Licence: US Government public domain (17 U.S.C. §105).

Emissions & fuel consumption

Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.

Year	CO₂ emitted	Fuel burned	Time at sea	CO₂ / n mile
2018	19,040 t	6,093 t	128 days	559 kg
2019	17,823 t	5,690 t	111 days	592 kg
2020	5,521 t	1,765 t	32 days	765 kg

Technical efficiency: EEDI (3.35 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

Port	Record	Date (UTC)	Berth	Source
Hong Kong HKHKG	Arrival	Jul 21, 2020, 12:23 UTC	WL	Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
PORT OF SOUTH LOUISIANA (LA)	Departure	Aug 2, 2015(date only)	—	USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)	Arrival	Jul 31, 2015(date only)	—	USACE foreign traffic vessel entrances & clearances
PAULSBORO, NJ	Departure	Mar 18, 2014(date only)	—	USACE foreign traffic vessel entrances & clearances
PAULSBORO, NJ	Arrival	Mar 17, 2014(date only)	—	USACE foreign traffic vessel entrances & clearances
PAULSBORO, NJ	Arrival	Nov 3, 2013(date only)	—	USACE foreign traffic vessel entrances & clearances
PAULSBORO, NJ	Departure	Nov 3, 2013(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Departure	Sep 20, 2013(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Arrival	Sep 19, 2013(date only)	—	USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)	Departure	Jun 11, 2012(date only)	—	USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)	Arrival	Jun 10, 2012(date only)	—	USACE foreign traffic vessel entrances & clearances
Texas City USTXT	Departure	Mar 24, 2012(date only)	—	USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: March 28, 2006.

Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.

Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.

Frequently asked questions

Where is Cape Brindisi now?: Voydar has no displayable AIS position for Cape Brindisi in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Cape Brindisi?: Cape Brindisi is an oil tanker, built in 2005 by HD Hyundai Heavy Industries. The vessel is 274 m long and has a gross tonnage of 81,076.
What sanctions and inspection records does Voydar hold for Cape Brindisi?: Cape Brindisi appears on the OFAC SDN list under SDGT. No matched inspection records are displayed for Cape Brindisi. 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/9293143

View JSON API documentationFree without a key for occasional use; use an API key for more.

Follow by RSS Open data

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