Skip to content

MEDKON CANAKKALE

Container ship · Panama · built 2007 · AIS Class A

IMO9341964MMSI352002364Call sign3E2292Last AIS position Oct 6, 2026, 13:35 UTC

In short

MEDKON CANAKKALE (Container ship, Panama flag) was last seen on AIS on , at anchor, in the port of Ashdod Southport. Its crew-entered AIS destination is ILASH (Ashdod); its reported draught is 7.7 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 12:20 UTC). It arrived there on Oct 5, 2026, 13:16 UTC. ISM manager: Okyanus Ege Denizcilik Ticaret A.S. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Container ship
Flag
Panama
Year built
2007
Gross tonnage
7,545
Size (length × beam)
130 m × 21 m

Watch this ship

Get an email when MEDKON CANAKKALE reaches Ashdod, and when it leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

Free forever. No card. A free account follows up to 5 ships and ports.

Photo of Conmar Gulf
Photo: Eduard47 · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
31.8451° N, 34.6102° E
Area
Mediterranean Sea
Speed
0 kn
Course
42°
Heading
315°
31.8451° N, 34.6102° E
Open the full live map →

Last 30 days: 4 port calls (Ashdod Southport, Firuzkoy, Haifa, and Ashdod).

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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
MEDKON CANAKKALE
IMO numberWhat is an IMO number?
9341964
MMSIWhat is an MMSI?
352002364
Call signWhat is a call sign?
3E2292
Flag
Panama
Vessel type
Container ship
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
7,545
Length overall
129.6 m
Beam
20.6 m
Year built
2007

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 years 2024–2025 · reported · confidence 0.9 · retrieved Oct 5, 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 Ashdod SouthportAIS-detectedVoydar port-call detector (AIS geofence)
Left FiruzkoyAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at FiruzkoyAIS-detectedVoydar port-call detector (AIS geofence)
Left HaifaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at HaifaAIS-detectedVoydar port-call detector (AIS geofence)
Former name: Jrs AlsterWikidata
Former name: Jrs CastorWikidata
Former name: LomurWikidata

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.

NameEvidenceDateSource
Jrs AlsterFormer nameJan 1, 2010Wikidata
Jrs CastorFormer nameJan 1, 2008Wikidata
LomurFormer nameJan 1, 2007Wikidata
Conmar GulfFormer name—Wikidata

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: Wikidata. Licence: CC0 1.0.

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
201813,017 t4,125 t238 days196 kg
201913,898 t4,405 t267 days187 kg
202010,271 t3,230 t162 days212 kg
202110,266 t3,242 t163 days220 kg
20229,854 t3,097 t165 days200 kg
20244,950 t1,584 t172 days144 kg
2025924 t295 t35 days155 kg

Technical efficiency: EEXI (30.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
Ashdod Southport ILASTOct 5, 2026, 13:16 UTCin port—
Firuzkoy TRFRZOct 2, 2026, 04:27 UTCOct 2, 2026, 09:45 UTC5 h 18 min
Haifa ILHFASep 25, 2026, 04:20 UTCSep 25, 2026, 11:48 UTC7 h 28 min
Ashdod ILASHSep 23, 2026, 21:14 UTCSep 24, 2026, 19:26 UTC22 h 12 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.

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
Sep 25, 2026, 11:18 UTC
Draught change

Reported draught went from 6.6 m to 5.5 m while in port at Haifa. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 24, 2026, 19:30 UTC
Draught change

Reported draught went from 7.5 m to 6.6 m after leaving Ashdod. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)

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

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 MEDKON CANAKKALE now?
MEDKON CANAKKALE (Container ship, Panama flag) was last seen on AIS on Oct 6, 2026, 13:35 UTC, at anchor, in the port of Ashdod Southport. The crew-entered destination was ILASH (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 12:20 UTC). This report does not confirm the ship’s current route.
What kind of ship is MEDKON CANAKKALE?
MEDKON CANAKKALE is a container ship sailing under the flag of Panama, built in 2007 by Fujian Mawei Shipbuilding. The vessel is 129.6 m long with a beam of 20.6 m and has a gross tonnage of 7,545.
Who is recorded as the owner or manager of MEDKON CANAKKALE?
Okyanus Ege Denizcilik Ticaret A.S. is recorded as ISM manager for MEDKON CANAKKALE (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 MEDKON CANAKKALE?
Voydar has no matched sanctions record displayed for MEDKON CANAKKALE 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 MEDKON CANAKKALE. 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/9341964
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