Where is MAERSK FINISTERRE now?

MAERSK FINISTERRE (Cargo ship, Singapore flag) was last seen on AIS on Oct 6, 2026, 14:31 UTC, under way at 20 kn, in the Mediterranean Sea. The crew-entered destination was LAST UPDATE TIME (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 14:18 UTC). This report does not confirm the ship’s current route.

What kind of ship is MAERSK FINISTERRE?

MAERSK FINISTERRE is a cargo ship sailing under the flag of Singapore.

What sanctions and inspection records does Voydar hold for MAERSK FINISTERRE?

Voydar has no matched sanctions record displayed for MAERSK FINISTERRE 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 MAERSK FINISTERRE. Missing records do not establish whether the ship has been detained.

MAERSK FINISTERRE

Cargo ship · Singapore · AIS Class A

IMO1013353MMSI563307600Call signDATAHUBLast AIS position Oct 6, 2026, 14:31 UTC

Open in Terminal

In short

MAERSK FINISTERRE (Cargo ship, Singapore flag) was last seen on AIS on Oct 6, 2026, 14:31 UTC, under way at 20 kn, in the Mediterranean Sea. Its crew-entered AIS destination is LAST UPDATE TIME; its reported draught is 10.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 14:18 UTC).

Current voyage: from Perama (departed Oct 4, 2026, 20:18 UTC) to LAST UPDATE TIME

Vessel type: Cargo ship
Flag: Singapore
Year built: —
Gross tonnage: —
Size (length × beam): —
Registered owner: —

Watch this ship

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

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

Last reported position

received Oct 6, 2026, 14:31 UTC

Position: 36.4099° N, 14.7124° E
Area: Mediterranean Sea
StatusWhat do AIS statuses mean?: Under way using engine
Speed: 20 kn
Course: 104°
Heading: 104°

36.4099° N, 14.7124° E

Open the full live map →

Last 30 days: 2 port calls (Perama and Tanger Med).

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: MAERSK FINISTERRE
IMO numberWhat is an IMO number?: 1013353
MMSIWhat is an MMSI?: 563307600
Call signWhat is a call sign?: DATAHUB
Flag: Singapore
Vessel type: Cargo ship
AIS ship type: Cargo (hazardous cat. D)
Gross tonnageGross tonnage vs deadweight: —
Length overall: —
Beam: —
Year built: —

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.

No owner, operator or manager is recorded for this vessel yet.

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 4, 2026, 20:18 UTC	Left PeramaAIS-detected	Voydar port-call detector (AIS geofence)
Oct 4, 2026, 19:25 UTC	Arrived at PeramaAIS-detected	Voydar port-call detector (AIS geofence)
Oct 4, 2026 (first seen)	Call sign changed from 9V9709 to DATAHUB	AIS, seen by Voydar
Sep 30, 2026, 07:33 UTC	Left Tanger MedAIS-detected	Voydar port-call detector (AIS geofence)
Sep 29, 2026, 15:47 UTC	Arrived at Tanger MedAIS-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.

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
Perama GRPER	Oct 4, 2026, 19:25 UTC	Oct 4, 2026, 20:18 UTC	53 min
Tanger Med MAPTM	Sep 29, 2026, 15:47 UTC	Sep 30, 2026, 07:33 UTC	15 h 45 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.

When	What we observed	Confidence
Oct 5, 2026, 12:31 UTC	Two positions This MMSI was reported in two places 855 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1	Medium (70%)
Oct 5, 2026, 12:19 UTC	Two positions This MMSI was reported in two places 850 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1	Medium (70%)
Oct 5, 2026, 10:18 UTC	Two positions This MMSI was reported in two places 808 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1	Medium (70%)
Oct 5, 2026, 09:50 UTC	Two positions This MMSI was reported in two places 805 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1	Medium (70%)
Oct 5, 2026, 09:38 UTC	Two positions This MMSI was reported in two places 805 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1	Medium (70%)
Oct 4, 2026, 19:31 UTC	Two positions This MMSI was reported in two places 805 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1	Medium (70%)
Oct 4, 2026, 19:16 UTC	Two positions This MMSI was reported in two places 804 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1	Medium (70%)
Oct 4, 2026, 19:01 UTC	Two positions This MMSI was reported in two places 804 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1	Medium (70%)
Oct 4, 2026, 18:21 UTC	Two positions This MMSI was reported in two places 804 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1	Medium (70%)
Oct 4, 2026, 18:01 UTC	Two positions This MMSI was reported in two places 804 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1	Medium (70%)
Oct 4, 2026, 17:47 UTC	Two positions This MMSI was reported in two places 806 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1	Medium (70%)
Oct 4, 2026, 17:17 UTC	Two positions This MMSI was reported in two places 809 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1	Medium (70%)
Oct 4, 2026, 17:04 UTC	Two positions This MMSI was reported in two places 810 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1	Medium (70%)
Oct 4, 2026, 15:31 UTC	Two positions This MMSI was reported in two places 817 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1	Medium (70%)

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 MAERSK FINISTERRE now?: MAERSK FINISTERRE (Cargo ship, Singapore flag) was last seen on AIS on Oct 6, 2026, 14:31 UTC, under way at 20 kn, in the Mediterranean Sea. The crew-entered destination was LAST UPDATE TIME (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 14:18 UTC). This report does not confirm the ship’s current route.
What kind of ship is MAERSK FINISTERRE?: MAERSK FINISTERRE is a cargo ship sailing under the flag of Singapore.
What sanctions and inspection records does Voydar hold for MAERSK FINISTERRE?: Voydar has no matched sanctions record displayed for MAERSK FINISTERRE 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 MAERSK FINISTERRE. 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/1013353

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