TROUBADOUR
General cargo ship · Latvia · built 2011 · AIS Class A
In short
TROUBADOUR (General cargo ship, Latvia flag) was last seen on AIS on , under way at 9.5 kn, in the North 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 ABERDEEN, with an ETA of Oct 5, 2026, 22:00 UTC; its reported draught is 3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 00:32 UTC). ISM manager: Baltnautic Shipping Ltd (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
Current voyage: from New Holland (departed Oct 2, 2026, 22:55 UTC) to ABERDEEN
- Vessel type
- General cargo ship
- Flag
- Latvia
- Year built
- 2011
- Gross tonnage
- —
- Size (length × beam)
- 88 m × 12 m
- ISM manager
- Baltnautic Shipping Ltd
Watch this ship
TROUBADOUR 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.
Last reported position
received- Position
- 54.857° N, 0.8128° W
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 9.5 kn
- Course
- 322°
- Heading
- 319°
Last 30 days: 1 port call (New Holland).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows TROUBADOUR's track before the last 30 days. Voydar has recorded its port calls since June 19, 2026.Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- TROUBADOUR
- IMO numberWhat is an IMO number?
- 9463865
- MMSIWhat is an MMSI?
- 275491000
- Call signWhat is a call sign?
- YLOZ
- Flag
- Latvia
- Vessel type
- General cargo ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- —
- Deadweight (DWT)
- Source: Wikidata, record Q83651584. Added to Voydar on September 23, 2026. Licence: CC0 1.0.2,570 t
- Length overall
- 87.5 m
- Beam
- 11.5 m
- Year built
- 2011
LatviaA 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
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 New HollandAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at New HollandAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left VargonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at VargonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left RiemeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at RiemeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at New YorkAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from New YorkAuthority-reported | USACE foreign traffic vessel entrances & clearances |
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 |
|---|---|---|---|---|
| 2025 | 1,623 t | 506 t | 159 days | 51 kg |
Technical efficiency: EEXI (20.13 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 |
|---|---|---|---|
| New Holland GBNHO | Sep 25, 2026, 17:42 UTC | Oct 2, 2026, 22:55 UTC | 7 d 5 h |
| Vargon SEVGN | Aug 31, 2026, 02:00 UTC | Sep 7, 2026, 06:04 UTC | 7 d 4 h |
| Rieme BERIE | Jun 19, 2026, 09:33 UTC | Jun 20, 2026, 09:04 UTC | 23 h 32 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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| New York USNYC | Arrival | Mar 14, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Departure | Mar 14, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: March 14, 2013.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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 |
|---|---|---|
| Oct 2, 2026, 19:15 UTC | Draught change Reported draught went from 3.6 m to 3 m while in port at New Holland. 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 TROUBADOUR now?
- TROUBADOUR (General cargo ship, Latvia flag) was last seen on AIS on Oct 5, 2026, 03:51 UTC, under way at 9.5 kn, in the North 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 ABERDEEN (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 00:32 UTC). This report does not confirm the ship’s current route.
- What kind of ship is TROUBADOUR?
- TROUBADOUR is a general cargo ship sailing under the flag of Latvia, built in 2011. The vessel is 87.5 m long with a beam of 11.5 m.
- Who is recorded as the owner or manager of TROUBADOUR?
- Baltnautic Shipping Ltd is recorded as ISM manager for TROUBADOUR (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 TROUBADOUR?
- Voydar has no matched sanctions record displayed for TROUBADOUR 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 TROUBADOUR. Missing records do not establish whether the ship has been detained.
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/9463865Using 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.