Skip to content

MV:ADRIATIC ROSE

ship · St. Kitts & Nevis · built 1995 · AIS Class A

IMO9115949MMSI341277002Call signV4YI6Last AIS position Sep 26, 2026, 17:04 UTC

In short

MV:ADRIATIC ROSE (ship, St. Kitts & Nevis flag) was last seen on AIS on , under way at 14.1 kn, in the North Atlantic Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is BRSSO (Sao Sebastiao), with an ETA of Oct 7, 2026, 06:00 UTC; its reported draught is 5.5 m (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 03:53 UTC). ISM manager: Devon Ship Management Ltd (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Current voyage: from Cartagena (departed Sep 23, 2026, 11:16 UTC) to BRSSO (Sao Sebastiao)

Vessel type
ship
Year built
1995
Gross tonnage
6,442
Size (length × beam)
122 m

Watch this ship

MV:ADRIATIC ROSE 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.

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

Photo of MV:ADRIATIC ROSE
Photo: Bahnfrend · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
25.7718° N, 15.8437° W
Area
North Atlantic Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
14.1 kn
Course
213°
Heading
208°
25.7718° N, 15.8437° W
Open the full live map →

Last 30 days: 1 port call (Cartagena).

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
MV:ADRIATIC ROSE
IMO numberWhat is an IMO number?
9115949
MMSIWhat is an MMSI?
341277002
Call signWhat is a call sign?
V4YI6
Vessel type
ship
Gross tonnageGross tonnage vs deadweight
6,442
Length overall
122.1 m
Beam
—
Year built
1995

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 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
Left CartagenaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at CartagenaAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)

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
20250 t0 t0 days—

Technical efficiency: Not Applicable. 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
Cartagena ESCARSep 22, 2026, 15:46 UTCSep 23, 2026, 11:16 UTC19 h 30 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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Hong Kong HKHKGArrival(matched by call sign)Apr 8, 2024, 00:33 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJan 14, 2024, 09:30 UTCNWLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJul 24, 2023, 19:34 UTCNLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMay 26, 2022, 03:56 UTCNWLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Oct 17, 2018, 02:53 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalAug 29, 2018, 00:35 UTCNWLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalAug 1, 2018, 19:45 UTCNWLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Wilmington USILGDepartureFeb 18, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Wilmington USILGArrivalFeb 18, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Wilmington USILGDepartureNov 30, 2007(date only)—USACE foreign traffic vessel entrances & clearances
Wilmington USILGArrivalNov 30, 2007(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: November 30, 2007.

Frequently asked questions

Where is MV:ADRIATIC ROSE now?
MV:ADRIATIC ROSE (ship, St. Kitts & Nevis flag) was last seen on AIS on Sep 26, 2026, 17:04 UTC, under way at 14.1 kn, in the North Atlantic Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was BRSSO (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 03:53 UTC). This report does not confirm the ship’s current route.
What kind of ship is MV:ADRIATIC ROSE?
MV:ADRIATIC ROSE is a ship sailing under the flag of St. Kitts & Nevis, built in 1995 by Scheepswerf Gebr. van Diepen, Waterhuizen. The vessel is 122.1 m long and has a gross tonnage of 6,442.
Who is recorded as the owner or manager of MV:ADRIATIC ROSE?
Devon Ship Management Ltd is recorded as ISM manager for MV:ADRIATIC ROSE (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 MV:ADRIATIC ROSE?
Voydar has no matched sanctions record displayed for MV:ADRIATIC ROSE 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 MV:ADRIATIC ROSE. 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/9115949
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