Ekmen
General cargo ship · San Marino · built 1996 · AIS Class B
In short
Ekmen (General cargo ship, San Marino flag) was last seen on AIS on , under way at 8.9 kn, in the Mediterranean Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its last detected port call was at Petit-Couronne: arrived Jun 9, 2026, left Jun 16, 2026. ISM manager: EKMEN DENIZCILIK VE TICARET LTD. STI. (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
- Vessel type
- General cargo ship
- Flag
- San Marino
- Year built
- 1996
- Gross tonnage
- 4,358
- Size (length × beam)
- 105 m × 17 m
- ISM manager
- EKMEN DENIZCILIK VE TICARET LTD. STI.
Watch this ship
Get an email when Ekmen 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 Ekmen.
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
received- Position
- 35.9094° N, 27.4835° E
- Area
- Mediterranean Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 8.9 kn
- Course
- 333°
- Heading
- 334°
Voydar detected no port call in the last 30 days.
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-upIdentity & particulars
- Name
- Ekmen
- IMO numberWhat is an IMO number?
- 9136888
- MMSIWhat is an MMSI?
- 268260900
- Call signWhat is a call sign?
- T7DP5
- Flag
- San Marino
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 4,358
- Deadweight (DWT)
- Source: Wikidata, record Q117082150. Added to Voydar on September 23, 2026. Licence: CC0 1.0.6,830 t
- Length overall
- 105 m
- Beam
- 16.8 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.
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting year 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.
| Date | Event | Source |
|---|---|---|
| Left Petit-CouronneAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Petit-CouronneAIS-detected | Voydar port-call detector (AIS geofence) | |
| Inspection at Tampa, Florida | USCG PSIX / CGMIX inspections | |
| Reported departure from TampaAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at TampaAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from New OrleansAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Inspection at New Orleans, Louisiana | USCG PSIX / CGMIX inspections | |
| Inspection at New Orleans, Louisiana | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Tampa, Florida | USCG PSIX / CGMIX inspections | |
| Inspection at Port Arthur, Texas | USCG PSIX / CGMIX inspections | |
| Inspection at Portsmouth, Virginia | USCG PSIX / CGMIX inspections | |
| Inspection at CORPUS CHRISTI, Texas | USCG PSIX / CGMIX inspections | |
| Inspection at VIRGINIA BEACH, Virginia | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at New Orleans, Louisiana | USCG PSIX / CGMIX inspections | |
| Inspection at VIRGINIA BEACH, Virginia | USCG PSIX / CGMIX inspections |
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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| May 15, 2009 | Vessel Inspection | Tampa, Florida | clean |
| Apr 7, 2009 | Vessel Inspection | New Orleans, Louisiana | clean |
| Apr 6, 2009 | Boarding | New Orleans, Louisiana | clean |
| Jun 12, 2008 | Vessel InspectionPSC | Tampa, Florida | clean |
| Mar 4, 2008 | Vessel Inspection | Port Arthur, Texas | clean |
| Nov 11, 2007 | Vessel Operational Control | Portsmouth, Virginia | clean |
| Oct 16, 2007 | Vessel Inspection | CORPUS CHRISTI, Texas | clean |
| Sep 27, 2007 | Boarding | VIRGINIA BEACH, Virginia | clean |
| Jun 26, 2007 | Vessel InspectionPSC | New Orleans, Louisiana | clean |
| Jun 6, 2007 | Boarding | VIRGINIA BEACH, Virginia | clean |
| Jan 26, 2007 | Boarding | Savannah, Georgia | clean |
| Jun 15, 2006 | Vessel InspectionPSC | Savannah, Georgia | clean |
| Mar 22, 2006 | Vessel InspectionPSC | STATEN ISLAND, New York | clean |
| Dec 26, 2005 | Vessel Inspection | Portsmouth, Virginia | clean |
| Aug 12, 2005 | Vessel InspectionPSC | Tampa, Florida | clean |
| Jul 27, 2005 | Boarding | Portsmouth, Virginia | clean |
| Jul 26, 2005 | Vessel Operational Control | Portsmouth, Virginia | clean |
| Jul 7, 2005 | Vessel Inspection | Savannah, Georgia | clean |
| Mar 28, 2005 | Vessel InspectionPSC | Tampa, Florida | clean |
| Oct 8, 2004 | Vessel InspectionPSC | Baltimore, Maryland | clean |
Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.
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 |
|---|---|---|---|---|
| 2025 | 959 t | 301 t | 102 days | 89 kg |
Technical efficiency: EEXI (14.08 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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Petit-Couronne FRPET | Jun 9, 2026, 05:36 UTC | Jun 16, 2026, 04:31 UTC | 6 d 22 h |
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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Tampa USTPA | Departure | May 15, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Tampa USTPA | Arrival | May 15, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Departure | May 13, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baton Rouge USBTR | Arrival | May 11, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Apr 29, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Apr 27, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baton Rouge USBTR | Departure | Apr 14, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baton Rouge USBTR | Arrival | Apr 7, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Tampa USTPA | Departure | Jan 12, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Tampa USTPA | Arrival | Jan 12, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Departure | Nov 3, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Arrival | Nov 3, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: January 10, 2002.
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 Ekmen now?
- Ekmen (General cargo ship, San Marino flag) was last seen on AIS on Sep 14, 2026, 16:37 UTC, under way at 8.9 kn, in the Mediterranean Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
- What kind of ship is Ekmen?
- Ekmen is a general cargo ship sailing under the flag of San Marino, built in 1996 by Sasebo Heavy Industries. The vessel is 105 m long with a beam of 16.8 m and has a gross tonnage of 4,358.
- Who is recorded as the owner or manager of Ekmen?
- EKMEN DENIZCILIK VE TICARET LTD. STI. is recorded as ISM manager for Ekmen (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for Ekmen?
- Voydar has no matched sanctions record displayed for Ekmen 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. Ekmen has 44 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
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/9136888Using 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.