Skip to content

BOXSTER

Tanker · Belgium · AIS Class A

IMONo IMOMMSI205419290Call signOT4192Last AIS position Oct 5, 2026, 01:29 UTC

In short

BOXSTER (Tanker, Belgium flag) was last seen on AIS on , not moving, near Hansweert/Schore (North Sea). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is ANTWERPEN INSTEEKDOH, with an ETA of Oct 5, 2026, 06:47 UTC; its reported draught is 3.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 01:24 UTC).

Current voyage: from Terneuzen (departed Sep 29, 2026, 16:18 UTC) to ANTWERPEN INSTEEKDOH

Vessel type
Tanker
Year built
—
Gross tonnage
—
Size (length × beam)
—
Registered owner
—

Watch this ship

BOXSTER has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.

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

Last reported position

received
Position
51.4388° N, 4.2342° E
Area
North Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0 kn
Course
210°
Heading
175°
51.4388° N, 4.2342° E
Open the full live map →

Last 30 days: 4 port calls (Terneuzen and Amsterdam).

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

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

Try the live demo, no sign-up

Identity & particulars

Name
BOXSTER
MMSIWhat is an MMSI?
205419290
Call signWhat is a call sign?
OT4192
Vessel type
Tanker
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.

DateEventSource
Left TerneuzenAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at TerneuzenAIS-detectedVoydar port-call detector (AIS geofence)
Left TerneuzenAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at TerneuzenAIS-detectedVoydar port-call detector (AIS geofence)
Left AmsterdamAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at AmsterdamAIS-detectedVoydar 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

PortArrivedDepartedTime in port
Terneuzen NLTNZSep 29, 2026, 08:10 UTCSep 29, 2026, 16:18 UTC8 h 8 min
Terneuzen NLTNZSep 24, 2026, 12:16 UTCSep 24, 2026, 13:55 UTC1 h 39 min
Amsterdam NLAMSSep 15, 2026, 07:14 UTCSep 16, 2026, 17:41 UTC34 h 27 min
Amsterdam NLAMSSep 14, 2026, 23:03 UTCSep 15, 2026, 07:11 UTC8 h 8 min
Amsterdam NLAMSJun 14, 2026, 19:17 UTCJun 21, 2026, 09:48 UTC6 d 14 h

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
Sep 30, 2026, 07:45 UTC
Draught change

Reported draught went from 1.5 m to 3.2 m after leaving Terneuzen. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)

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 BOXSTER now?
BOXSTER (Tanker, Belgium flag) was last seen on AIS on Oct 5, 2026, 01:29 UTC, not moving, near Hansweert/Schore (North Sea). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was ANTWERPEN INSTEEKDOH (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 01:24 UTC). This report does not confirm the ship’s current route.
What kind of ship is BOXSTER?
BOXSTER is a tanker sailing under the flag of Belgium.
What sanctions and inspection records does Voydar hold for BOXSTER?
Voydar has no matched sanctions record displayed for BOXSTER 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 BOXSTER. 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/mmsi-205419290
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