Ulusoy 14
Ro-ro ship · Türkiye · built 2012 · AIS Class A
In short
Ulusoy 14 (Ro-ro ship, Türkiye flag) was last seen on AIS on , under way at 15.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 crew-entered AIS destination is ITTRS-TRCES, with an ETA of Oct 2, 2026, 10:00 UTC; its reported draught is 6.6 m (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 22:39 UTC). ISM manager: Ulusoy Ro/Ro Isletmeleri (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Trieste (departed Sep 29, 2026, 22:01 UTC) to ITTRS-TRCES
- Vessel type
- Ro-ro ship
- Flag
- Türkiye
- Year built
- 2012
- Gross tonnage
- 31,540
- Size (length × beam)
- 208 m
- ISM manager
- Ulusoy Ro/Ro Isletmeleri
Watch this ship
Get an email when Ulusoy 14 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 Ulusoy 14.
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
- 38.4837° N, 19.9801° E
- Area
- Mediterranean Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 15.9 kn
- Course
- 150°
- Heading
- 146°
Last 30 days: 3 port calls (Trieste and Muggia).
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
- Ulusoy 14
- IMO numberWhat is an IMO number?
- 9506253
- MMSIWhat is an MMSI?
- 271043164
- Call signWhat is a call sign?
- TCUP3
- Flag
- Türkiye
- AIS ship type
- Cargo (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- 31,540
- Length overall
- 208 m
- Beam
- —
- Year built
- 2012
TürkiyeA 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 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 TriesteAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at TriesteAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left TriesteAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at TriesteAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left MuggiaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at MuggiaAIS-detected | Voydar 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.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 27,880 t | 8,949 t | 231 days | 304 kg |
| 2019 | 24,101 t | 7,736 t | 193 days | 308 kg |
| 2020 | 32,190 t | 10,320 t | 253 days | 322 kg |
| 2021 | 31,749 t | 10,172 t | 253 days | 330 kg |
| 2022 | 33,032 t | 10,599 t | 253 days | 343 kg |
| 2023 | 31,960 t | 10,255 t | 250 days | 335 kg |
| 2024 | 30,633 t | 9,828 t | 253 days | 323 kg |
| 2025 | 29,048 t | 9,319 t | 247 days | 319 kg |
Technical efficiency: EIV (27.68 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 |
|---|---|---|---|
| Trieste ITTRS | Sep 29, 2026, 19:21 UTC | Sep 29, 2026, 22:01 UTC | 2 h 40 min |
| Trieste ITTRS | Sep 28, 2026, 14:35 UTC | Sep 29, 2026, 18:57 UTC | 28 h 22 min |
| Muggia ITUGG | Sep 8, 2026, 07:41 UTC | Sep 22, 2026, 21:54 UTC | 14 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.
| When | What we observed | Confidence |
|---|---|---|
| Sep 30, 2026, 21:58 UTC | Draught change Reported draught went from 2.8 m to 6.6 m after leaving Trieste. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 30, 2026, 03:19 UTC | Draught change Reported draught went from 6.6 m to 2.8 m after leaving Trieste. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
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.
Frequently asked questions
- Where is Ulusoy 14 now?
- Ulusoy 14 (Ro-ro ship, Türkiye flag) was last seen on AIS on Oct 1, 2026, 07:54 UTC, under way at 15.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. The crew-entered destination was ITTRS-TRCES (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 22:39 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Ulusoy 14?
- Ulusoy 14 is a ro-ro ship sailing under the flag of Türkiye, built in 2012 by Flensburger Schiffbau-Gesellschaft. The vessel is 208 m long and has a gross tonnage of 31,540.
- Who is recorded as the owner or manager of Ulusoy 14?
- Ulusoy Ro/Ro Isletmeleri is recorded as ISM manager for Ulusoy 14 (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 Ulusoy 14?
- Voydar has no matched sanctions record displayed for Ulusoy 14 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. No matched inspection records are displayed for Ulusoy 14. Missing records do not establish whether the ship has been detained.
Sister ships
Likely sister ships: built by Flensburger Schiffbau-Gesellschaft, same type, gross tonnage within 2.5% and length within 1.5% of this ship's.
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/9506253Using 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.