Skip to content

IMO 8208713

Bulk carrier · built 1984

IMO8208713No AIS position on record

In short

IMO 8208713 (Bulk carrier) has no AIS position on record with Voydar.

Vessel type
Bulk carrier
Flag
—
Year built
1984
Gross tonnage
35,886
Size (length × beam)
225 m
Registered owner
—

Watch this ship

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

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 8208713
Photo: Moshi Anahory · Licence: CC BY-SA 2.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

Name
IMO 8208713
IMO numberWhat is an IMO number?
8208713
Flag
—
Vessel type
Bulk carrier
Gross tonnageGross tonnage vs deadweight
35,886
Length overall
225 m
Beam
—
Year built
1984

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.

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 PORT OF SOUTH LOUISIANA (LA)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at New OrleansAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from PORT OF SOUTH LOUISIANA (LA)Authority-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.

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
PORT OF SOUTH LOUISIANA (LA)DepartureJan 2, 2008(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalDec 20, 2007(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureNov 8, 2006(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)ArrivalNov 7, 2006(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureNov 12, 2005(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)ArrivalNov 3, 2005(date only)—USACE foreign traffic vessel entrances & clearances
MATAGORDA SHIP CHANNEL, TX (PORT LAVACA/POINT COMFORT, TX)DepartureOct 28, 2005(date only)—USACE foreign traffic vessel entrances & clearances
MATAGORDA SHIP CHANNEL, TX (PORT LAVACA/POINT COMFORT, TX)ArrivalOct 27, 2005(date only)—USACE foreign traffic vessel entrances & clearances
Mobile USMOBDepartureAug 6, 2004(date only)—USACE foreign traffic vessel entrances & clearances
Mobile USMOBArrivalAug 5, 2004(date only)—USACE foreign traffic vessel entrances & clearances
MATAGORDA SHIP CHANNEL, TXDepartureAug 2, 2004(date only)—USACE foreign traffic vessel entrances & clearances
MATAGORDA SHIP CHANNEL, TXArrivalJul 30, 2004(date only)—USACE foreign traffic vessel entrances & clearances

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

About IMO 8208713

MV Fedra was a Liberian-registered bulk-carrier cargo ship. It ran aground and smashed against Europa Point, the southernmost tip of Gibraltar on 10 October 2008 following severe gale force winds measuring 12 on the Beaufort scale. Spanish and Gibraltarian emergency services mounted a joint rescue operation, Gibraltar declared a Major Incident and requested the standby of additional statutory and voluntary emergency services (including St John Ambulance Gibraltar), although due to the safe rescue of all crew from Fedra they were ultimately not needed. Five of its 31 crew members were airlifted to safety by a Spanish coast guard helicopter and the rest were hoisted up by an improvised crane system. The vessel broke in half shortly thereafter. About half of its 300 tons of fuel spilled into the sea.

Summary from Wikipedia, licensed CC BY-SA.

Frequently asked questions

Where is IMO 8208713 now?
Voydar has no displayable AIS position for IMO 8208713 in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is IMO 8208713?
IMO 8208713 is a bulk carrier, built in 1984 by Burmeister & Wain. The vessel is 225 m long and has a gross tonnage of 35,886.
What sanctions and inspection records does Voydar hold for IMO 8208713?
Voydar has no matched sanctions record displayed for IMO 8208713 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 IMO 8208713. 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/8208713
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