ISABELL
Tanker · Netherlands · AIS Class A
In short
ISABELL (Tanker, Netherlands flag) was last seen on AIS on , moored, in the Baltic Sea. Its crew-entered AIS destination is HAMBURG; its reported draught is 2.2 m (voyage report via AISstream.io global terrestrial AIS, received Nov 16, 2026, 13:31 UTC).
Current voyage: from Brunsbuttel (departed Nov 16, 2026, 01:51 UTC) to HAMBURG
- Vessel type
- Tanker
- Flag
- Netherlands
- Year built
- —
- Gross tonnage
- —
- Size, AIS-reported (length × beam)
- 86 m × 12 m
- Registered owner
- —
Last reported position: 54.3782° N, 10.1769° E · Baltic Sea · See on the map
Watch this ship
Get an email when ISABELL arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
What you would have been told
Following ISABELL over the last 24 hours would have sent 3 messages.
- LeftBrunsbuttel
- ArrivedBrunsbuttel
- LeftHamburg
Detected from AIS, as of Nov 16, 2026, 14:38 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for ISABELL reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans
Get alerts on your phone: Voydar for iPhone
Last reported position
received- Position
- 54.3782° N, 10.1769° E
- Area
- Baltic Sea
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0.1 kn
- Course
- —
- Heading
- —
Locator map: Natural Earth (public domain)
Last 30 days: 6 port calls (Brunsbuttel and Hamburg).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows ISABELL's track before the last 30 days. Voydar has recorded its port calls since September 21, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
- Name
- ISABELL
- IMO numberWhat is an IMO number?
- —
- MMSIWhat is an MMSI?
- 244670102
- Call signWhat is a call sign?
- PD5117
- Flag
- Netherlands
- Vessel type
- Tanker
- Gross tonnageGross tonnage vs deadweight
- —
- Length (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 16, 2026.86 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 16, 2026.12 m
- 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.
AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via AISstream.io global terrestrial AIS on November 16, 2026.
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.
Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →
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 BrunsbuttelAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BrunsbuttelAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HamburgAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HamburgAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HamburgAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HamburgAIS-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 |
|---|---|---|---|
| Brunsbuttel DEBRB | Nov 15, 2026, 23:51 UTC | Nov 16, 2026, 01:51 UTC | 2 h 0 min |
| Hamburg DEHAM | Nov 8, 2026, 08:14 UTC | Nov 15, 2026, 20:54 UTC | 7 d 12 h |
| Hamburg DEHAM | Oct 30, 2026, 02:21 UTC | Nov 6, 2026, 18:29 UTC | 7 d 16 h |
| Hamburg DEHAM | Oct 26, 2026, 15:21 UTC | Oct 27, 2026, 23:12 UTC | 31 h 51 min |
| Hamburg DEHAM | Oct 22, 2026, 05:05 UTC | Oct 26, 2026, 07:15 UTC | 4 d 2 h |
| Hamburg DEHAM | Oct 21, 2026, 05:14 UTC | Oct 21, 2026, 11:55 UTC | 6 h 40 min |
| Hamburg DEHAM | Oct 17, 2026, 14:28 UTC | Oct 20, 2026, 16:37 UTC | 3 d 2 h |
| Hamburg DEHAM | Oct 14, 2026, 16:30 UTC | Oct 17, 2026, 08:05 UTC | 2 d 15 h |
| Hamburg DEHAM | Oct 8, 2026, 22:38 UTC | Oct 14, 2026, 01:07 UTC | 5 d 2 h |
| Hamburg DEHAM | Sep 29, 2026, 03:02 UTC | Oct 8, 2026, 13:04 UTC | 9 d 10 h |
| Hamburg DEHAM | Sep 27, 2026, 20:57 UTC | Sep 28, 2026, 05:57 UTC | 9 h 0 min |
| Hamburg DEHAM | Sep 21, 2026, 09:49 UTC | Sep 25, 2026, 17:55 UTC | 4 d 8 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 |
|---|---|---|
| Oct 27, 2026, 17:51 UTC | Draught change Reported draught went from 2.4 m to 3.6 m while in port at Hamburg. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 21, 2026, 11:56 UTC | Draught change Reported draught went from 2 m to 2.9 m after leaving Hamburg. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 28, 2026, 15:07 UTC | Draught change Reported draught went from 2.8 m to 2.3 m after leaving Hamburg. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 28, 2026, 05:19 UTC | Draught change Reported draught went from 2.3 m to 2.8 m while in port at Hamburg. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
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
- What kind of ship is ISABELL?
- ISABELL is a tanker sailing under the flag of Netherlands.
- What sanctions and inspection records does Voydar hold for ISABELL?
- Voydar has no matched sanctions record displayed for ISABELL 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 ISABELL. Missing records do not establish whether the ship has been detained.
More Tankers
Other tankers with full Voydar profiles, those under the flag of Netherlands first. A different set each day. All tankers
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-244670102Cite this page
ISABELL. Voydar (voydar.com). https://www.voydar.com/vessel/mmsi-244670102-isabell. Retrieved November 16, 2026.
Each fact above names its own source and date. Cite that primary source too when you rely on a fact.
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.