GERTRUIDA
Cargo ship · Netherlands · AIS Class A
In short
GERTRUIDA (Cargo ship, Netherlands flag) was last seen on AIS on , not moving, near IJmuiden/Velsen (North Sea). Its last detected port call was at Rotterdam: arrived Sep 30, 2026, left Sep 30, 2026.
- Vessel type
- Cargo ship
- Flag
- Netherlands
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- Registered owner
- —
Watch this ship
Get an email when GERTRUIDA arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
That creates your free account and follows GERTRUIDA. Free forever. No card.
Free forever. No card. A free account follows up to 5 ships and ports.
By continuing you accept the Terms and the Privacy policy.
Last reported position
received- Position
- 52.6094° N, 4.7659° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 0 kn
- Course
- —
- Heading
- —
Last 30 days: 4 port calls (Rotterdam, 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 GERTRUIDA's track before the last 30 days. Voydar has recorded its port calls since June 10, 2026.Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- GERTRUIDA
- IMO numberWhat is an IMO number?
- —
- MMSIWhat is an MMSI?
- 244750554
- Call signWhat is a call sign?
- PG4758
- Flag
- Netherlands
- Vessel type
- Cargo ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- Year built
- —
NetherlandsA 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 |
|---|---|---|
| Left RotterdamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at RotterdamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left ZaandamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ZaandamAIS-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 |
|---|---|---|---|
| Rotterdam NLRTM | Sep 30, 2026, 17:52 UTC | Sep 30, 2026, 19:33 UTC | 1 h 41 min |
| Zaandam NLZAA | Sep 22, 2026, 19:58 UTC | Sep 23, 2026, 04:14 UTC | 8 h 16 min |
| Amsterdam NLAMS | Sep 21, 2026, 08:57 UTC | Sep 22, 2026, 09:19 UTC | 24 h 22 min |
| Amsterdam NLAMS | Sep 16, 2026, 08:57 UTC | Sep 16, 2026, 17:20 UTC | 8 h 23 min |
| Rotterdam NLRTM | Jun 16, 2026, 09:40 UTC | Jun 26, 2026, 13:02 UTC | 10 d 3 h |
| Rotterdam NLRTM | Jun 10, 2026, 17:01 UTC | Jun 15, 2026, 05:26 UTC | 4 d 12 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.
| When | What we observed | Confidence |
|---|---|---|
| Sep 26, 2026, 10:49 UTC | Two positions This MMSI was reported in two places 1,006 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 26, 2026, 09:02 UTC | Two positions This MMSI was reported in two places 1,012 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 26, 2026, 08:16 UTC | Two positions This MMSI was reported in two places 1,010 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 26, 2026, 08:01 UTC | Two positions This MMSI was reported in two places 1,010 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 26, 2026, 07:46 UTC | Two positions This MMSI was reported in two places 1,009 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 26, 2026, 07:33 UTC | Two positions This MMSI was reported in two places 1,009 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 26, 2026, 07:19 UTC | Two positions This MMSI was reported in two places 1,009 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 23, 2026, 09:01 UTC | Two positions This MMSI was reported in two places 1,003 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 22, 2026, 18:34 UTC | Position jump Reported position moved 994 km in 556 min, faster than any ship can travel. The broadcast position was wrong for a time; GNSS interference, equipment faults and manipulation are all possible causes. Method seadar.behaviour.position_jump v1 | Medium (60%) |
| Sep 21, 2026, 14:17 UTC | Two positions This MMSI was reported in two places 970 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
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 GERTRUIDA now?
- GERTRUIDA (Cargo ship, Netherlands flag) was last seen on AIS on Oct 5, 2026, 01:39 UTC, not moving, near IJmuiden/Velsen (North Sea).
- What kind of ship is GERTRUIDA?
- GERTRUIDA is a cargo ship sailing under the flag of Netherlands.
- What sanctions and inspection records does Voydar hold for GERTRUIDA?
- Voydar has no matched sanctions record displayed for GERTRUIDA 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 GERTRUIDA. 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-244750554Using 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.