EURASIA
Tanker · Switzerland · AIS Class A
In short
EURASIA (Tanker, Switzerland flag) was last seen on AIS on , moored, in the port of Zaandam. Its crew-entered AIS destination is AMSTERDAM JAN VAN RI; its reported draught is 2.9 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 18:12 UTC). It arrived there on Oct 2, 2026, 15:28 UTC.
- Vessel type
- Tanker
- Flag
- Switzerland
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- Registered owner
- —
Watch this ship
Get an email when EURASIA 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 EURASIA.
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.
Last reported position
received- Position
- 52.4109° N, 4.8373° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 95°
- Heading
- —
Last 30 days: 6 port calls (Zaandam, Antwerpen, Amsterdam, Delfzijl, and Rotterdam).
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)
Try the live demo, no sign-upIdentity & particulars
- Name
- EURASIA
- IMO numberWhat is an IMO number?
- —
- MMSIWhat is an MMSI?
- 269057726
- Call signWhat is a call sign?
- HE7726
- Flag
- Switzerland
- Vessel type
- Tanker
- AIS ship type
- Tanker (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- Year built
- —
SwitzerlandA 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 |
|---|---|---|
| Arrived at ZaandamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left AntwerpenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at AntwerpenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left AmsterdamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at AmsterdamAIS-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 |
|---|---|---|---|
| Zaandam NLZAA | Oct 2, 2026, 15:28 UTC | in port | — |
| Antwerpen BEANR | Sep 30, 2026, 21:23 UTC | Oct 2, 2026, 00:13 UTC | 26 h 49 min |
| Amsterdam NLAMS | Sep 26, 2026, 23:59 UTC | Sep 27, 2026, 01:13 UTC | 1 h 14 min |
| Delfzijl NLDZL | Sep 25, 2026, 20:24 UTC | Sep 25, 2026, 21:13 UTC | 50 min |
| Amsterdam NLAMS | Sep 25, 2026, 01:55 UTC | Sep 25, 2026, 03:05 UTC | 1 h 10 min |
| Rotterdam NLRTM | Sep 24, 2026, 16:47 UTC | Sep 24, 2026, 19:27 UTC | 2 h 41 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 2, 2026, 00:14 UTC | Draught change Reported draught went from 1.6 m to 2.9 m after leaving Antwerpen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 26, 2026, 06:27 UTC | Draught change Reported draught went from 2.5 m to 1.6 m after leaving Delfzijl. 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.
Frequently asked questions
- Where is EURASIA now?
- EURASIA (Tanker, Switzerland flag) was last seen on AIS on Oct 3, 2026, 18:17 UTC, moored, in the port of Zaandam. The crew-entered destination was AMSTERDAM JAN VAN RI (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 18:12 UTC). This report does not confirm the ship’s current route.
- What kind of ship is EURASIA?
- EURASIA is a tanker sailing under the flag of Switzerland.
- What sanctions and inspection records does Voydar hold for EURASIA?
- Voydar has no matched sanctions record displayed for EURASIA 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 EURASIA. 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-269057726Using 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.