Skip to content
voydar.com

Amadeus Gold

Pleasure craft · Netherlands · built 2010 · AIS Class A

IMO9479565MMSI244810730Call signPBKULast AIS position Nov 20, 2026, 12:20 UTC

In short

Amadeus Gold (Pleasure craft, Netherlands flag) was last seen on AIS on , under way at 6 kn, in the Bay of Biscay. Its crew-entered AIS destination is BURELA, with an ETA of Nov 22, 2026, 05:00 UTC; its reported draught is 3.2 m (voyage report via AISstream.io global terrestrial AIS, received Nov 20, 2026, 09:20 UTC). Its last detected port call was at Montoir-de-Bretagne: arrived Nov 9, 2026, left Nov 20, 2026. Registered owner: Amadeus Gold B.V. (source: ILT — Nederlands vlagregister (Netherlands flag register data)).

Vessel type
Pleasure craft
Year built
2010
Gross tonnage
1,767
Size (length × beam)
88 m × 11 m
Registered owner
Amadeus Gold B.V.

Last reported position: 47.0159° N, 2.5187° W · Bay of Biscay · See on the map

Watch this ship

Get an email when Amadeus Gold arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

What you would have been told

Following Amadeus Gold over the last 24 hours would have sent 1 message.

Detected from AIS, as of Nov 20, 2026, 12:21 UTC.

Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Amadeus Gold reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans

Get alerts on your phone: the Voydar app

Last reported position

received
Position
47.0159° N, 2.5187° W
Area
Bay of Biscay
Status
Under way using engineWhat do AIS statuses mean?
Speed
6 kn
Course
228°
Heading
235°
Compass: course over ground 228°, heading 235°
NArrow: course. Hull: heading. As broadcast on AIS.
47.0159° N, 2.5187° W. Reference map only, not for navigation.
Locator map: Natural Earth (public domain)
47.0159° N, 2.5187° W
See it live in 3D →

Last 30 days: 10 port calls (Montoir-de-Bretagne, Moerdijk, Rotterdam, Terneuzen, Antwerpen, Wijnegem, Lillo, Brunsbuttel, Holtenau, and Abenra).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

Pro shows Amadeus Gold's track before the last 30 days. Voydar has recorded its port calls since October 18, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.

Try the live demo, no sign-up

Identity & particulars

Length overall 87.5 mone tick every 10 m

Beam 11.3 mPlan outline, to scale

Drawn by Voydar from the recorded type, length and beam. The side view is a drawing of the ship type, not of this ship; the length rule and the plan outline's proportions are to scale, the hull shape is not surveyed.
Name
Amadeus Gold
IMO numberWhat is an IMO number?
9479565
MMSIWhat is an MMSI?
244810730
Vessel type
Pleasure craft
Gross tonnageGross tonnage vs deadweight
1,767
Length overall
87.5 m
Beam
11.3 m
Year built
2010

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.

Registered owner
Amadeus Gold B.V.(not linked to a company record)
Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · high confidence · retrieved Nov 19, 2026
ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · high confidence · retrieved Nov 16, 2026
Builder
DAMEN BERGUM(not linked to a company record)
Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · high confidence · retrieved Nov 19, 2026

Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →

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 Montoir-de-BretagneAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Montoir-de-BretagneAIS-detectedVoydar port-call detector (AIS geofence)
Left MoerdijkAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at MoerdijkAIS-detectedVoydar port-call detector (AIS geofence)
Left RotterdamAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at RotterdamAIS-detectedVoydar port-call detector (AIS geofence)
Former name: STELLEAIS, seen by Voydar
Call sign changed from PB9549 to PBKUPHAIS, seen by Voydar

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
STELLEFormer name, change seen on AISSep 22, 2026AIS (vessel's own broadcast)

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.

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
20251,725 t538 t210 days44 kg

Technical efficiency: EEXI (16.67 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.

Compared with ships of its type

Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “General cargo ship”. Lower is less CO₂.

CO₂ per nautical mile sailed44.3 kg per nautical mile
Lowest reportedHighest reported

4% of the 2,956 ships in this group reported a lower figure.

Group: lower quartile 74.8 · median 110.6 · upper quartile 185.8

Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated

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

Time in port over the last 34 days, drawn by Voydar from the AIS-detected calls listed below. Each bar runs from arrival to departure; gaps are time away from a detected port or without reception.
PortArrivedDepartedTime in port
Montoir-de-Bretagne FRMTXNov 9, 2026, 23:06 UTCNov 20, 2026, 09:29 UTC10 d 10 h
Moerdijk NLMOENov 6, 2026, 00:42 UTCNov 6, 2026, 18:01 UTC17 h 19 min
Rotterdam NLRTMNov 5, 2026, 05:51 UTCNov 5, 2026, 23:39 UTC17 h 48 min
Terneuzen NLTNZOct 28, 2026, 04:00 UTCOct 29, 2026, 00:31 UTC20 h 32 min
Antwerpen BEANROct 27, 2026, 22:36 UTCOct 28, 2026, 00:49 UTC2 h 13 min
Wijnegem BEWJGOct 25, 2026, 10:58 UTCOct 27, 2026, 11:07 UTC2 d 0 h
Lillo BELILOct 25, 2026, 08:55 UTCOct 25, 2026, 09:51 UTC56 min
Brunsbuttel DEBRBOct 23, 2026, 09:31 UTCOct 23, 2026, 10:45 UTC1 h 15 min
Holtenau DEHTUOct 23, 2026, 01:11 UTCOct 23, 2026, 02:25 UTC1 h 14 min
Abenra DKAABOct 22, 2026, 03:23 UTCOct 22, 2026, 18:51 UTC15 h 28 min
Holtenau DEHTUOct 18, 2026, 19:42 UTCOct 18, 2026, 20:57 UTC1 h 15 min
Kiel Canal DECKLOct 18, 2026, 08:07 UTCOct 18, 2026, 12:28 UTC4 h 21 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
Nov 19, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 653 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 18, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 653 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 17, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 653 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 16, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 653 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 15, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 653 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 12, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 653 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 11, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 653 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 10, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 653 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 9, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 655 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 7, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 324 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 6, 2026, 18:04 UTC
Draught change

Reported draught went from 2.8 m to 4.1 m after leaving Moerdijk. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)
Nov 6, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 72 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

Medium (70%)
Nov 5, 2026, 22:00 UTC
Draught change

Reported draught went from 3.7 m to 2.8 m while in port at Rotterdam. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 29, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 269 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Oct 28, 2026, 22:37 UTC
Draught change

Reported draught went from 2.6 m to 4.1 m while in port at Terneuzen. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 27, 2026, 21:49 UTC
Draught change

Reported draught went from 3.4 m to 2.6 m after leaving Wijnegem. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)
Oct 25, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 54 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

Medium (70%)
Oct 24, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 80 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

Medium (70%)
Oct 23, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 428 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Oct 22, 2026, 00:00 UTC
IMO used twice

IMO 9479565 was broadcast by two ships (MMSI 244810726 and 244810730) 527 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)

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

What kind of ship is Amadeus Gold?
Amadeus Gold is a pleasure craft sailing under the flag of Netherlands, built in 2010. The vessel is 87.5 m long with a beam of 11.3 m and has a gross tonnage of 1,767.
Who is recorded as the owner or manager of Amadeus Gold?
Amadeus Gold B.V. is recorded as Registered owner for Amadeus Gold (source: ILT — Nederlands vlagregister (Netherlands flag register data)). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for Amadeus Gold?
Voydar has no matched sanctions record displayed for Amadeus Gold 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 Amadeus Gold. Missing records do not establish whether the ship has been detained.

Full Vessel Report

A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.

See a sample report (PDF)

Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.

Every fact on this page stays free.

Know this ship?

Help other readers. Member posts are shown as member content, never as sourced data.

  • Date, place and an optional note
  • Members who know her can answer
  • Suggest a correctionChecked against sources before anything changes

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/9479565
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Cite this page

Amadeus Gold. Voydar (voydar.com). https://www.voydar.com/vessel/9479565-amadeus-gold. Retrieved November 20, 2026.

Each fact above names its own source and date. Cite that primary source too when you rely on a fact.

Using this data in code?

Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.

See plans

Sources and attribution

  • AIS data: AISstream.io (none published)
  • Bron: Inspectie Leefomgeving en Transport (ILT), Vlagregister data (CC0 1.0). (CC0 1.0 (ilent.nl site-wide))
  • Wikidata (CC0 1.0)

Each fact above names its source and the date it was retrieved. Each source's licence applies to its data.

Compiled by Voydar from the sources named on this page.

Page: https://www.voydar.com/vessel/9479565-amadeus-gold

Generated from voydar.com on Nov 20, 2026, 12:21 UTC