Where is Matador 3 now?

Matador 3 (Other, Netherlands flag) was last seen on AIS on Oct 6, 2026, 10:08 UTC, not moving, near Schiedam (North Sea). The crew-entered destination was ROTTERDAM (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 09:49 UTC). This report does not confirm the ship’s current route.

What kind of ship is Matador 3?

Matador 3 is a other sailing under the flag of Netherlands, built in 2003 by Mangalia Shipyard. The vessel is 67 m long and has a gross tonnage of 3,898.

What sanctions and inspection records does Voydar hold for Matador 3?

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

Matador 3

Other · Netherlands · built 2003 · AIS Class A

IMO9272137MMSI246300000Call signPBHFLast AIS position Oct 6, 2026, 10:08 UTC

Open in Terminal

In short

Matador 3 (Other, Netherlands flag) was last seen on AIS on Oct 6, 2026, 10:08 UTC, not moving, near Schiedam (North Sea). Its crew-entered AIS destination is ROTTERDAM; its reported draught is 3.2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 09:49 UTC). Registered owner: Bonn & Mees Drijvende Bokken Beheer B.V. (source: ILT — Nederlands vlagregister (Netherlands flag register data)).

Current voyage: from Pernis (departed Sep 15, 2026, 17:19 UTC) to ROTTERDAM

Vessel type: Other
Flag: Netherlands
Year built: 2003
Gross tonnage: 3,898
Size (length × beam): 67 m
Registered owner: Bonn & Mees Drijvende Bokken Beheer B.V.

Watch this ship

Get an email when Matador 3 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, 10:08 UTC

Position: 51.8978° N, 4.432° E
Area: North Sea
StatusWhat do AIS statuses mean?: Restricted manoeuvrability
Speed: 0.1 kn
Course: 293°
Heading: 331°

51.8978° N, 4.432° E

Open the full live map →

Last 30 days: 2 port calls (Pernis and Poortugaal).

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

Pro shows Matador 3's track before the last 30 days. Voydar has recorded its port calls since July 1, 2026.Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name: Matador 3
IMO numberWhat is an IMO number?: 9272137
MMSIWhat is an MMSI?: 246300000
Call signWhat is a call sign?: PBHF
Flag: Netherlands
Vessel type: Other
Gross tonnageGross tonnage vs deadweight: 3,898
Net tonnage: Source: ILT — Nederlands vlagregister (Netherlands flag register data), record 40022. Added to Voydar on September 28, 2026. Licence: CC0 1.0 (ilent.nl site-wide).1,169
Length overall: 67 m
Beam: —
Year built: 2003

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: Bonn & Mees Drijvende Bokken Beheer B.V.(not linked to a company record)
Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · confidence 0.9 · retrieved Oct 1, 2026
Builder: Mangalia Shipyard
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
DAEWOO MANGALIA HEAVY INDUSTRIES SA(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
Sep 15, 2026, 17:19 UTC	Left PernisAIS-detected	Voydar port-call detector (AIS geofence)
Sep 15, 2026, 16:40 UTC	Arrived at PernisAIS-detected	Voydar port-call detector (AIS geofence)
Sep 15, 2026, 16:40 UTC	Left PoortugaalAIS-detected	Voydar port-call detector (AIS geofence)
Sep 15, 2026, 06:26 UTC	Arrived at PoortugaalAIS-detected	Voydar port-call detector (AIS geofence)
Aug 31, 2026, 05:18 UTC	Left PernisAIS-detected	Voydar port-call detector (AIS geofence)
Aug 25, 2026, 06:35 UTC	Arrived at PernisAIS-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
Pernis NLPER	Sep 15, 2026, 16:40 UTC	Sep 15, 2026, 17:19 UTC	39 min
Poortugaal NLPTG	Sep 15, 2026, 06:26 UTC	Sep 15, 2026, 16:40 UTC	10 h 14 min
Pernis NLPER	Aug 25, 2026, 06:35 UTC	Aug 31, 2026, 05:18 UTC	5 d 22 h
Rotterdam NLRTM	Jul 14, 2026, 11:46 UTC	Jul 16, 2026, 12:25 UTC	2 d 0 h
Pernis NLPER	Jul 4, 2026, 12:16 UTC	Jul 10, 2026, 05:24 UTC	5 d 17 h
Pernis NLPER	Jul 4, 2026, 10:39 UTC	Jul 4, 2026, 12:16 UTC	1 h 38 min
Pernis NLPER	Jul 4, 2026, 08:35 UTC	Jul 4, 2026, 10:39 UTC	2 h 3 min
Poortugaal NLPTG	Jul 3, 2026, 15:24 UTC	Jul 4, 2026, 08:35 UTC	17 h 11 min
Pernis NLPER	Jul 3, 2026, 12:12 UTC	Jul 3, 2026, 15:24 UTC	3 h 12 min
Pernis NLPER	Jul 2, 2026, 13:17 UTC	Jul 3, 2026, 12:12 UTC	22 h 56 min
Poortugaal NLPTG	Jul 2, 2026, 09:46 UTC	Jul 2, 2026, 13:16 UTC	3 h 30 min
Poortugaal NLPTG	Jul 1, 2026, 15:58 UTC	Jul 2, 2026, 09:46 UTC	17 h 48 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.

Frequently asked questions

Where is Matador 3 now?: Matador 3 (Other, Netherlands flag) was last seen on AIS on Oct 6, 2026, 10:08 UTC, not moving, near Schiedam (North Sea). The crew-entered destination was ROTTERDAM (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 09:49 UTC). This report does not confirm the ship’s current route.
What kind of ship is Matador 3?: Matador 3 is a other sailing under the flag of Netherlands, built in 2003 by Mangalia Shipyard. The vessel is 67 m long and has a gross tonnage of 3,898.
Who is recorded as the owner or manager of Matador 3?: Bonn & Mees Drijvende Bokken Beheer B.V. is recorded as Registered owner for Matador 3 (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 Matador 3?: Voydar has no matched sanctions record displayed for Matador 3 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 Matador 3. 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/9272137

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