YE 42 Anna Elizabeth
Fishing vessel · Netherlands · built 1987 · AIS Class A
In short
YE 42 Anna Elizabeth (Fishing vessel, Netherlands flag) was last seen on AIS on , not moving, near Hansweert/Schore (North Sea). Its crew-entered AIS destination is YERSEKE; its reported draught is 0.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 21:31 UTC).
Current voyage: from Kats (departed Oct 1, 2026, 11:48 UTC) to YERSEKE
- Vessel type
- Fishing vessel
- Flag
- Netherlands
- Year built
- 1987
- Gross tonnage
- 267
- Size (length × beam)
- 40 m
- Registered owner
- —
Watch this ship
Get an email when YE 42 Anna Elizabeth 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 YE 42 Anna Elizabeth.
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
- 51.4851° N, 4.0581° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 0 kn
- Course
- —
- Heading
- 7°
Last 30 days: at least 12 port calls (Kats, Burghsluis, Dreischor, Scharendijke, Wilhelminadorp, Veere, and Stavenisse).
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
- YE 42 Anna Elizabeth
- IMO numberWhat is an IMO number?
- 8706284
- MMSIWhat is an MMSI?
- 246027000
- Call signWhat is a call sign?
- PCRI
- Flag
- Netherlands
- Vessel type
- Fishing vessel
- AIS ship type
- Fishing
- Gross tonnageGross tonnage vs deadweight
- 267
- Length overall
- 40.1 m
- Beam
- —
- Year built
- 1987
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.
| Date | Event | Source |
|---|---|---|
| Left KatsAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KatsAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left BurghsluisAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BurghsluisAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left DreischorAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at DreischorAIS-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 |
|---|---|---|---|
| Kats NLKAT | Oct 1, 2026, 10:14 UTC | Oct 1, 2026, 11:48 UTC | 1 h 34 min |
| Burghsluis NLBHS | Sep 30, 2026, 14:59 UTC | Sep 30, 2026, 18:25 UTC | 3 h 26 min |
| Dreischor NLND5 | Sep 23, 2026, 12:58 UTC | Sep 23, 2026, 15:42 UTC | 2 h 43 min |
| Scharendijke NLSRD | Sep 22, 2026, 13:16 UTC | Sep 23, 2026, 11:27 UTC | 22 h 10 min |
| Kats NLKAT | Sep 17, 2026, 08:56 UTC | Sep 22, 2026, 07:11 UTC | 4 d 22 h |
| Kats NLKAT | Sep 17, 2026, 07:46 UTC | Sep 17, 2026, 08:49 UTC | 1 h 3 min |
| Wilhelminadorp NLWHD | Sep 16, 2026, 15:34 UTC | Sep 17, 2026, 06:12 UTC | 14 h 39 min |
| Veere NLVER | Sep 16, 2026, 09:14 UTC | Sep 16, 2026, 15:34 UTC | 6 h 19 min |
| Veere NLVER | Sep 16, 2026, 07:41 UTC | Sep 16, 2026, 08:37 UTC | 56 min |
| Veere NLVER | Sep 15, 2026, 08:36 UTC | Sep 15, 2026, 09:50 UTC | 1 h 14 min |
| Kats NLKAT | Sep 14, 2026, 08:12 UTC | Sep 14, 2026, 08:54 UTC | 41 min |
| Stavenisse NLSVN | Sep 9, 2026, 12:35 UTC | Sep 9, 2026, 14:20 UTC | 1 h 45 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.
Frequently asked questions
- Where is YE 42 Anna Elizabeth now?
- YE 42 Anna Elizabeth (Fishing vessel, Netherlands flag) was last seen on AIS on Oct 1, 2026, 21:36 UTC, not moving, near Hansweert/Schore (North Sea). The crew-entered destination was YERSEKE (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 21:31 UTC). This report does not confirm the ship’s current route.
- What kind of ship is YE 42 Anna Elizabeth?
- YE 42 Anna Elizabeth is a fishing vessel sailing under the flag of Netherlands, built in 1987. The vessel is 40.1 m long and has a gross tonnage of 267.
- What sanctions and inspection records does Voydar hold for YE 42 Anna Elizabeth?
- Voydar has no matched sanctions record displayed for YE 42 Anna Elizabeth 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 YE 42 Anna Elizabeth. 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/8706284Using 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.