Skip to content

EDMY

General cargo ship · Portugal · built 2002 · AIS Class A

IMO9263540MMSI255806175Call signCQAH5Last AIS position Oct 3, 2026, 17:45 UTC

In short

EDMY (General cargo ship, Portugal flag) was last seen on AIS on , under way at 10.1 kn, in the North Sea. Its crew-entered AIS destination is NOSIP (Skipavik - Gulen), with an ETA of Oct 5, 2026, 18:00 UTC; its reported draught is 5.4 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 17:13 UTC). ISM manager: Myklebusthaug Management AS (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Current voyage: from IJmuiden/Velsen (departed Oct 3, 2026, 08:10 UTC) to NOSIP (Skipavik - Gulen)

Year built
2002
Gross tonnage
4,938
Size (length × beam)
119 m × 15 m

Watch this ship

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

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 EDMY
Photo: Farid mernissi · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
53.8713° N, 4.9782° E
Area
North Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
10.1 kn
Course
21°
Heading
25°
53.8713° N, 4.9782° E
Open the full live map →

Last 30 days: 4 port calls (IJmuiden/Velsen, Ramsvika, and Leixoes).

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-up

Identity & particulars

Name
EDMY
IMO numberWhat is an IMO number?
9263540
MMSIWhat is an MMSI?
255806175
Call signWhat is a call sign?
CQAH5
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
4,938
Length overall
118.6 m
Beam
15.4 m
Year built
2002

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.

DateEventSource
Left IJmuiden/VelsenAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at IJmuiden/VelsenAIS-detectedVoydar port-call detector (AIS geofence)
Left IJmuiden/VelsenAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at IJmuiden/VelsenAIS-detectedVoydar port-call detector (AIS geofence)
Left RamsvikaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at RamsvikaAIS-detectedVoydar port-call detector (AIS geofence)

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
20256,682 t2,084 t217 days118 kg

Technical efficiency: EEXI (9.51 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
IJmuiden/Velsen NLIJMOct 3, 2026, 07:26 UTCOct 3, 2026, 08:10 UTC44 min
IJmuiden/Velsen NLIJMOct 2, 2026, 08:56 UTCOct 2, 2026, 09:34 UTC39 min
Ramsvika NORMVSep 27, 2026, 14:13 UTCSep 28, 2026, 20:38 UTC30 h 25 min
Leixoes PTLEISep 12, 2026, 15:44 UTCSep 27, 2026, 14:13 UTC14 d 22 h
Skalevik NOSKVAug 15, 2026, 15:16 UTCAug 15, 2026, 18:33 UTC3 h 18 min
Valberg NOVBEJul 17, 2026, 03:21 UTCJul 17, 2026, 19:45 UTC16 h 24 min
Breiviga NOBVRJul 6, 2026, 12:19 UTCJul 7, 2026, 06:40 UTC18 h 21 min
Skalevik NOSKVJun 16, 2026, 22:43 UTCJun 17, 2026, 00:59 UTC2 h 16 min
Lutelandet NOLULJun 15, 2026, 22:38 UTCJun 16, 2026, 15:44 UTC17 h 6 min
IJmuiden/Velsen NLIJMJun 13, 2026, 07:50 UTCJun 15, 2026, 22:37 UTC2 d 14 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.

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.

Predicted arrival

Voydar estimates arrival at Amsterdam around Oct 6, 2026, 19:57 UTC, most likely between Oct 3, 2026, 11:38 UTC and Oct 23, 2026, 00:07 UTC. Based on 76 past transits between NLIJM and Amsterdam seen in our port calls. The crew-reported ETA is Oct 2, 2026, 10:00 UTC.

Medium (56%) · Method seadar.behaviour.eta_prediction v1

WhenWhat we observedConfidence
Oct 3, 2026, 05:30 UTC
Draught change

Reported draught went from 7.4 m to 5.4 m after leaving IJmuiden/Velsen. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 27, 2026, 14:52 UTC
Draught change

Reported draught went from 5.4 m to 7.4 m while in port at Ramsvika. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

High (75%)

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

Source: BarentsWatch AIS API. Contains data under NLOD made available by BarentsWatch. Licence: NLOD 2.0 (probable).

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 EDMY now?
EDMY (General cargo ship, Portugal flag) was last seen on AIS on Oct 3, 2026, 17:45 UTC, under way at 10.1 kn, in the North Sea. The crew-entered destination was NOSIP (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 17:13 UTC). This report does not confirm the ship’s current route.
What kind of ship is EDMY?
EDMY is a general cargo ship sailing under the flag of Portugal, built in 2002 by Bodewes Shipyards. The vessel is 118.6 m long with a beam of 15.4 m and has a gross tonnage of 4,938.
Who is recorded as the owner or manager of EDMY?
Myklebusthaug Management AS is recorded as ISM manager for EDMY (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 EDMY?
Voydar has no matched sanctions record displayed for EDMY 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 EDMY. 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/9263540
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