Skip to content

GOOD MOVE

Tanker · Netherlands · AIS Class A

IMONo IMOMMSI244790994Call signPA5650Last AIS position Oct 5, 2026, 16:33 UTC

In short

GOOD MOVE (Tanker, Netherlands flag) was last seen on AIS on , not moving, in the port of Zaandam. Its crew-entered AIS destination is AMSTERDAM; its reported draught is 1.9 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 15:30 UTC). It arrived there on Oct 5, 2026, 10:48 UTC.

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

Watch this ship

Get an email when GOOD MOVE 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
Position
52.4119° N, 4.8531° E
Area
North Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0 kn
Course
—
Heading
—
52.4119° N, 4.8531° E
Open the full live map →

Last 30 days: 6 port calls (Zaandam 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 GOOD MOVE's track before the last 30 days. Voydar has recorded its port calls since June 9, 2026.Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
GOOD MOVE
MMSIWhat is an MMSI?
244790994
Call signWhat is a call sign?
PA5650
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
Arrived at ZaandamAIS-detectedVoydar port-call detector (AIS geofence)
Left ZaandamAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at ZaandamAIS-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
Zaandam NLZAAOct 5, 2026, 10:48 UTCin port—
Zaandam NLZAAOct 3, 2026, 11:06 UTCOct 5, 2026, 08:12 UTC45 h 6 min
Amsterdam NLAMSOct 1, 2026, 10:07 UTCOct 2, 2026, 20:59 UTC34 h 52 min
Zaandam NLZAASep 28, 2026, 11:37 UTCSep 28, 2026, 12:47 UTC1 h 10 min
Zaandam NLZAASep 26, 2026, 13:33 UTCSep 28, 2026, 08:28 UTC42 h 55 min
Amsterdam NLAMSSep 23, 2026, 11:22 UTCSep 26, 2026, 10:00 UTC2 d 22 h
Amsterdam NLAMSJul 28, 2026, 13:26 UTCAug 5, 2026, 09:31 UTC7 d 20 h
IJmuiden/Velsen NLIJMJun 19, 2026, 11:55 UTCJun 19, 2026, 12:55 UTC1 h 0 min
Amsterdam NLAMSJun 19, 2026, 08:06 UTCJun 19, 2026, 08:44 UTC38 min
IJmuiden/Velsen NLIJMJun 16, 2026, 10:36 UTCJun 19, 2026, 06:13 UTC2 d 19 h
Amsterdam NLAMSJun 9, 2026, 09:04 UTCJun 9, 2026, 10:52 UTC1 h 47 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.

WhenWhat we observedConfidence
Sep 28, 2026, 21:07 UTC
Draught change

Reported draught went from 2.8 m to 1.9 m after leaving Zaandam. Voydar infers the ship probably discharged 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 GOOD MOVE now?
GOOD MOVE (Tanker, Netherlands flag) was last seen on AIS on Oct 5, 2026, 16:33 UTC, not moving, in the port of Zaandam. The crew-entered destination was AMSTERDAM (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 15:30 UTC). This report does not confirm the ship’s current route.
What kind of ship is GOOD MOVE?
GOOD MOVE is a tanker sailing under the flag of Netherlands.
What sanctions and inspection records does Voydar hold for GOOD MOVE?
Voydar has no matched sanctions record displayed for GOOD MOVE 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 GOOD MOVE. 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-244790994
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