Skip to content

VB FALCON

Tug · Belgium · built 1997 · AIS Class A

IMO9120190MMSI205233000Call signORKQLast AIS position Oct 1, 2026, 13:03 UTC

In short

VB FALCON (Tug, Belgium flag) was last seen on AIS on , moored, in the port of Schiedam. Its crew-entered AIS destination is ROTTERDAM; its reported draught is 5.2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 12:42 UTC). It arrived there on Oct 1, 2026, 05:30 UTC.

Vessel type
Tug
Year built
1997
Gross tonnage
398
Size (length × beam)
30 m × 11 m
Registered owner
—

Watch this ship

Get an email when VB FALCON arrives or 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 VB FALCON.

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.

Photo of VB FALCON
Photo: Alf van Beem · Licence: CC0 · via Wikimedia Commons

Last reported position

received
Position
51.8998° N, 4.3973° E
Area
North Sea
Speed
0 kn
Course
49°
Heading
237°
51.8998° N, 4.3973° E
Open the full live map →

Last 30 days: at least 12 port calls (Schiedam, Botlek, and Rotterdam).

Port calls are detected by Seadar 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)

Try the live demo, no sign-up

Identity & particulars

Name
VB FALCON
IMO numberWhat is an IMO number?
9120190
MMSIWhat is an MMSI?
205233000
AIS ship type
Other
Length overall
30 m
Beam
11 m
Year built
1997

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.

Builder
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026

Timeline

Dated events for this ship from every source Seadar holds, newest first. Each line names its source; derived items say how they were derived.

DateEventSource
Arrived at SchiedamAIS-detectedSeadar port-call detector (AIS geofence)
Left BotlekAIS-detectedSeadar port-call detector (AIS geofence)
Arrived at BotlekAIS-detectedSeadar port-call detector (AIS geofence)
Left RotterdamAIS-detectedSeadar port-call detector (AIS geofence)
Arrived at RotterdamAIS-detectedSeadar port-call detector (AIS geofence)
Former name: Union 11Wikidata

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
Union 11Former nameJan 1, 1997Wikidata

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 Seadar saw them.

Source: Wikidata. Licence: CC0 1.0.

Port calls

Two kinds of evidence, kept apart: calls Seadar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Schiedam NLSCIOct 1, 2026, 05:30 UTCin port—
Botlek NLBOTOct 1, 2026, 00:34 UTCOct 1, 2026, 05:30 UTC4 h 56 min
Rotterdam NLRTMSep 30, 2026, 20:17 UTCOct 1, 2026, 00:27 UTC4 h 10 min
Schiedam NLSCISep 25, 2026, 18:24 UTCSep 30, 2026, 17:02 UTC4 d 22 h
Botlek NLBOTSep 25, 2026, 12:58 UTCSep 25, 2026, 18:21 UTC5 h 23 min
Rotterdam NLRTMSep 25, 2026, 11:10 UTCSep 25, 2026, 12:54 UTC1 h 44 min
Schiedam NLSCISep 24, 2026, 18:32 UTCSep 24, 2026, 20:08 UTC1 h 37 min
Botlek NLBOTSep 24, 2026, 16:15 UTCSep 24, 2026, 18:30 UTC2 h 15 min
Schiedam NLSCISep 24, 2026, 09:15 UTCSep 24, 2026, 14:43 UTC5 h 28 min
Botlek NLBOTSep 24, 2026, 08:10 UTCSep 24, 2026, 09:13 UTC1 h 3 min
Schiedam NLSCISep 23, 2026, 15:39 UTCSep 24, 2026, 07:25 UTC15 h 46 min
Botlek NLBOTSep 23, 2026, 12:19 UTCSep 23, 2026, 15:38 UTC3 h 20 min

Detected by Seadar 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 VB FALCON now?
VB FALCON (Tug, Belgium flag) was last seen on AIS on Oct 1, 2026, 13:03 UTC, moored, in the port of Schiedam. The crew-entered destination was ROTTERDAM (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 12:42 UTC). This report does not confirm the ship’s current route.
What kind of ship is VB FALCON?
VB FALCON is a tug sailing under the flag of Belgium, built in 1997 by Astilleros Armon. The vessel is 30 m long with a beam of 11 m and has a gross tonnage of 398.
What sanctions and inspection records does Seadar hold for VB FALCON?
Seadar has no matched sanctions record displayed for VB FALCON from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for VB FALCON. 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/9120190
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

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