JAG AMOL
Bulk carrier · Marshall Islands · built 2015 · AIS Class A
In short
JAG AMOL (Bulk carrier, Marshall Islands flag) was last seen on AIS on , at anchor, in the North Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is DEBRB (Brunsbuttel), with an ETA of Oct 1, 2026, 03:00 UTC; its reported draught is 14.6 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 04:47 UTC).
- Vessel type
- Bulk carrier
- Flag
- Marshall Islands
- Year built
- 2015
- Gross tonnage
- 43,184
- Size (length × beam)
- 228 m × 32 m
- Registered owner
- —
Watch this ship
Get an email when JAG AMOL 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 JAG AMOL.
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
- 54.0862° N, 7.7268° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- At anchor
- Speed
- 0 kn
- Course
- 257°
- Heading
- 99°
Voydar detected no port call in the last 30 days.
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
- JAG AMOL
- IMO numberWhat is an IMO number?
- 9676113
- MMSIWhat is an MMSI?
- 538011982
- Call signWhat is a call sign?
- V7A3764
- Flag
- Marshall Islands
- Vessel type
- Bulk carrier
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 43,184
- Deadweight (DWT)
- Source: Wikidata, record Q117028724. Added to Voydar on September 23, 2026. Licence: CC0 1.0.81,843 t
- Length overall
- 228 m
- Beam
- 32 m
- Year built
- 2015
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.
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Sep 28, 2026Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Sep 28, 2026
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
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 |
|---|---|---|
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
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.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2019 | 5,407 t | 1,733 t | 70 days | 269 kg |
| 2020 | 12,879 t | 4,123 t | 146 days | 301 kg |
| 2021 | 3,249 t | 1,036 t | 55 days | 274 kg |
| 2022 | 2,955 t | 946 t | 43 days | 262 kg |
| 2025 | 4,749 t | 1,518 t | 73 days | 240 kg |
Technical efficiency: EEXI (3.47 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival(matched by call sign) | Jun 20, 2024, 08:38 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | May 24, 2023, 21:13 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Mar 11, 2023, 01:51 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Aug 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF PLAQUEMINES, LA | Arrival | Jul 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Arrival | Jul 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Departure | Jul 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Departure | May 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Arrival | May 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Departure | May 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Arrival | May 15, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Arrival | Apr 2, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: September 10, 2015.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is JAG AMOL now?
- JAG AMOL (Bulk carrier, Marshall Islands flag) was last seen on AIS on Oct 1, 2026, 05:17 UTC, at anchor, in the North Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was DEBRB (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 04:47 UTC). This report does not confirm the ship’s current route.
- What kind of ship is JAG AMOL?
- JAG AMOL is a bulk carrier sailing under the flag of Marshall Islands, built in 2015 by Tsuneishi Shipbuilding. The vessel is 228 m long with a beam of 32 m and has a gross tonnage of 43,184.
- What sanctions and inspection records does Voydar hold for JAG AMOL?
- Voydar has no matched sanctions record displayed for JAG AMOL 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 JAG AMOL. 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/9676113Using 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.