Where is RLO MERCHANT now?

RLO MERCHANT (Tanker, Netherlands flag) was last seen on AIS on Oct 4, 2026, 21:38 UTC, near Gravelines (North Sea). The crew-entered destination was FRDKK (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 17:18 UTC). This report does not confirm the ship’s current route.

What kind of ship is RLO MERCHANT?

RLO MERCHANT is a tanker sailing under the flag of Netherlands, built in 2004. The vessel is 88.4 m long with a beam of 13 m and has a gross tonnage of 2,314.

What sanctions and inspection records does Voydar hold for RLO MERCHANT?

Voydar has no matched sanctions record displayed for RLO MERCHANT 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. RLO MERCHANT has 1 recorded Port State Control inspection. Detention and deficiency detail is not recorded for these inspections.

RLO MERCHANT

Tanker · Netherlands · built 2004 · AIS Class A

IMO9305350MMSI245323000Call signPDFMLast AIS position Oct 4, 2026, 21:38 UTC

Open in Terminal

In short

RLO MERCHANT (Tanker, Netherlands flag) was last seen on AIS on Oct 4, 2026, 21:38 UTC, near Gravelines (North Sea). Its crew-entered AIS destination is FRDKK (Dunkerque), with an ETA of Oct 4, 2026, 12:00 UTC; its reported draught is 5.7 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 17:18 UTC). Registered owner: Antalya Shipping Limited (source: ILT — Nederlands vlagregister (Netherlands flag register data)).

Current voyage: from Esbjerg (departed Oct 2, 2026, 19:27 UTC) to FRDKK (Dunkerque)

Vessel type: Tanker
Flag: Netherlands
Year built: 2004
Gross tonnage: 2,314
Size (length × beam): 88 m × 13 m
Registered owner: Antalya Shipping Limited

Watch this ship

Get an email when RLO MERCHANT reaches Dunkerque, and when it 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 RLO MERCHANT.

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 Oct 4, 2026, 21:38 UTC

Position: 51.0176° N, 2.175° E
Area: North Sea
StatusWhat do AIS statuses mean?: Under way using engine
Speed: 0.6 kn
Course: 250°
Heading: 80°

51.0176° N, 2.175° E

Open the full live map →

Last 30 days: 3 port calls (Esbjerg, Pernis, and Botlek).

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

Pro shows RLO MERCHANT's track before the last 30 days. Voydar has recorded its port calls since June 9, 2026.

Try the live demo, no sign-up

Identity & particulars

Name: RLO MERCHANT
IMO numberWhat is an IMO number?: 9305350
MMSIWhat is an MMSI?: 245323000
Call signWhat is a call sign?: PDFM
Flag: Netherlands
Vessel type: Tanker
Gross tonnageGross tonnage vs deadweight: 2,314
Net tonnage: Source: ILT — Nederlands vlagregister (Netherlands flag register data), record 47932. Added to Voydar on September 28, 2026. Licence: CC0 1.0 (ilent.nl site-wide).1,045
Deadweight (DWT): Source: Wikidata, record Q83649440. Added to Voydar on September 23, 2026. Licence: CC0 1.0.3,446 t
Length overall: 88.4 m
Beam: 13 m
Year built: 2004

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: Antalya Shipping Limited(not linked to a company record)
Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · confidence 0.9 · retrieved Oct 1, 2026
Builder: CELIKTRANS(not linked to a company record)
Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · confidence 0.9 · retrieved Oct 1, 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
Oct 2, 2026, 19:27 UTC	Left EsbjergAIS-detected	Voydar port-call detector (AIS geofence)
Oct 1, 2026, 11:31 UTC	Arrived at EsbjergAIS-detected	Voydar port-call detector (AIS geofence)
Sep 30, 2026, 01:40 UTC	Left PernisAIS-detected	Voydar port-call detector (AIS geofence)
Sep 28, 2026, 16:16 UTC	Arrived at PernisAIS-detected	Voydar port-call detector (AIS geofence)
Sep 26, 2026, 11:40 UTC	Left BotlekAIS-detected	Voydar port-call detector (AIS geofence)
Sep 25, 2026, 11:01 UTC	Arrived at BotlekAIS-detected	Voydar port-call detector (AIS geofence)
Oct 12, 2012	Port State Control inspection at Savannah, Georgia	USCG PSIX / CGMIX inspections
Oct 12, 2012	Reported departure from SavannahAuthority-reported	USACE foreign traffic vessel entrances & clearances
Oct 12, 2012	Reported arrival at SavannahAuthority-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.

Safety & inspections

Inspections

not recorded

Detentions

Deficiencies

Date	Type	Port	Findings
Oct 12, 2012	Vessel InspectionPSC	Savannah, Georgia	clean

Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.

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
Esbjerg DKEBJ	Oct 1, 2026, 11:31 UTC	Oct 2, 2026, 19:27 UTC	31 h 56 min
Pernis NLPER	Sep 28, 2026, 16:16 UTC	Sep 30, 2026, 01:40 UTC	33 h 24 min
Botlek NLBOT	Sep 25, 2026, 11:01 UTC	Sep 26, 2026, 11:40 UTC	24 h 39 min
Kiel Canal DECKL	Jun 19, 2026, 21:17 UTC	Jun 19, 2026, 22:20 UTC	1 h 3 min
Kiel DEKEL	Jun 15, 2026, 22:57 UTC	Jun 16, 2026, 00:04 UTC	1 h 7 min
Warnemunde DEWAR	Jun 15, 2026, 06:32 UTC	Jun 15, 2026, 12:03 UTC	5 h 30 min
Warnemunde DEWAR	Jun 9, 2026, 11:29 UTC	Jun 10, 2026, 16:27 UTC	28 h 58 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
Savannah USSAV	Departure	Oct 12, 2012(date only)	—	USACE foreign traffic vessel entrances & clearances
Savannah USSAV	Arrival	Oct 12, 2012(date only)	—	USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: October 12, 2012.

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
Sep 26, 2026, 08:48 UTC	Draught change Reported draught went from 4.4 m to 5.1 m while in port at Botlek. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1	Medium (65%)

When

What we observed

Confidence

Sep 26, 2026, 08:48 UTC

Draught change

Reported draught went from 4.4 m to 5.1 m while in port at Botlek. Voydar infers the ship probably loaded 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.

How these are computed →

Frequently asked questions

Where is RLO MERCHANT now?: RLO MERCHANT (Tanker, Netherlands flag) was last seen on AIS on Oct 4, 2026, 21:38 UTC, near Gravelines (North Sea). The crew-entered destination was FRDKK (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 17:18 UTC). This report does not confirm the ship’s current route.
What kind of ship is RLO MERCHANT?: RLO MERCHANT is a tanker sailing under the flag of Netherlands, built in 2004. The vessel is 88.4 m long with a beam of 13 m and has a gross tonnage of 2,314.
Who is recorded as the owner or manager of RLO MERCHANT?: Antalya Shipping Limited is recorded as Registered owner for RLO MERCHANT (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 RLO MERCHANT?: Voydar has no matched sanctions record displayed for RLO MERCHANT 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. RLO MERCHANT has 1 recorded Port State Control inspection. Detention and deficiency detail is not recorded for these inspections.

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/9305350

View JSON API documentationFree without a key for occasional use; use an API key for more.

Follow by RSS Open data

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