Skip to content

Jag Aabha

Oil tanker · India · built 2008 · AIS Class A

IMO9388948MMSI419746000Call signAUUQLast AIS position Oct 5, 2026, 01:30 UTC

In short

Jag Aabha (Oil tanker, India flag) was last seen on AIS on , moored, near Zaandam (North Sea). Its crew-entered AIS destination is NL AMS (Amsterdam); its reported draught is 8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 00:25 UTC). ISM manager: The Great Eastern Shipping Co. Ltd. (source: EU MRV (THETIS-MRV) emissions, reporting year 2024).

Current voyage: from IJmuiden/Velsen (departed Oct 2, 2026, 22:10 UTC) to NL AMS (Amsterdam)

Vessel type
Oil tanker
Flag
India
Year built
2008
Gross tonnage
42,403
Size (length × beam)
228 m × 32 m

Watch this ship

Get an email when Jag Aabha reaches Amsterdam, and when it 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 Jag Aabha. 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.4179° N, 4.7487° E
Area
North Sea
Speed
0 kn
Course
26°
Heading
169°
52.4179° N, 4.7487° E
Open the full live map →

Last 30 days: 2 port calls (IJmuiden/Velsen and Le Havre).

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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
Jag Aabha
IMO numberWhat is an IMO number?
9388948
MMSIWhat is an MMSI?
419746000
Flag
India
AIS ship type
Tanker
Gross tonnageGross tonnage vs deadweight
42,403
Length overall
228 m
Beam
32.2 m
Year built
2008

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 2024 · reported · confidence 0.9 · retrieved Sep 28, 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.

DateEventSource
Left IJmuiden/VelsenAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at IJmuiden/VelsenAIS-detectedVoydar port-call detector (AIS geofence)
Left Le HavreAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Le HavreAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from New OrleansAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at PORT OF SOUTH LOUISIANA (LA)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from New YorkAuthority-reportedUSACE foreign traffic vessel entrances & clearances

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.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20204,229 t1,339 t39 days367 kg
20227,213 t2,302 t56 days433 kg
20233,547 t1,132 t33 days372 kg
20247,416 t2,378 t96 days305 kg

Technical efficiency: EEXI (4.08 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.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
IJmuiden/Velsen NLIJMOct 2, 2026, 21:09 UTCOct 2, 2026, 22:10 UTC1 h 1 min
Le Havre FRLEHSep 27, 2026, 08:46 UTCOct 1, 2026, 10:07 UTC4 d 1 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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
New Orleans USMSYDepartureAug 1, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)ArrivalJul 27, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCDepartureJul 13, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalJul 12, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Port Arthur USPOADepartureSep 23, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Port Arthur USPOAArrivalSep 23, 2015(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCDepartureOct 3, 2011(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalSep 30, 2011(date only)—USACE foreign traffic vessel entrances & clearances
PAULSBORO, NJDepartureSep 26, 2011(date only)—USACE foreign traffic vessel entrances & clearances
PAULSBORO, NJArrivalSep 25, 2011(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: September 25, 2011.

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.

Predicted arrival

Voydar estimates arrival at Amsterdam around Oct 9, 2026, 08:13 UTC, most likely between Oct 6, 2026, 00:12 UTC and Oct 25, 2026, 18:59 UTC. Based on 80 past transits between NLIJM and Amsterdam seen in our port calls. The crew-reported ETA is Oct 2, 2026, 13:00 UTC.

Medium (57%) · Method seadar.behaviour.eta_prediction v1

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.

How these are computed →

Frequently asked questions

Where is Jag Aabha now?
Jag Aabha (Oil tanker, India flag) was last seen on AIS on Oct 5, 2026, 01:30 UTC, moored, near Zaandam (North Sea). The crew-entered destination was NL AMS (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 00:25 UTC). This report does not confirm the ship’s current route.
What kind of ship is Jag Aabha?
Jag Aabha is an oil tanker sailing under the flag of India, built in 2008. The vessel is 228 m long with a beam of 32.2 m and has a gross tonnage of 42,403.
Who is recorded as the owner or manager of Jag Aabha?
The Great Eastern Shipping Co. Ltd. is recorded as ISM manager for Jag Aabha (source: EU MRV (THETIS-MRV) emissions; reporting year 2024). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for Jag Aabha?
Voydar has no matched sanctions record displayed for Jag Aabha 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 Jag Aabha. 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/9388948
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

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.

See plans