Skip to content

GISELE

Oil tanker · Liberia · built 2007 · AIS Class B

IMO9321196MMSI636026392Call signA8TP2Last AIS position Sep 29, 2026, 00:53 UTC

In short

GISELE (Oil tanker, Liberia flag) was last seen on AIS on , under way at 12.8 kn, in the Java Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its last detected port call was at Keppel: arrived Sep 26, 2026, left Sep 26, 2026. ISM manager: Fleet Management Limited (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Vessel type
Oil tanker
Year built
2007
Gross tonnage
40,953
Size (length × beam)
228 m × 32 m

Watch this ship

GISELE has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.

We email you a link and a code. That creates a free account, no password or card, and follows GISELE.

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.

Photo of GISELE
Photo: ---=XEON=--- · Licence: CC BY 3.0 · via Wikimedia Commons

Last reported position

received
Position
5.4931° S, 106.0594° E
Area
Java Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
12.8 kn
Course
210°
Heading
205°
5.4931° S, 106.0594° E
Open the full live map →

Last 30 days: 2 port calls (Keppel and Tanjung Pelepas).

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-up

Identity & particulars

Name
GISELE
IMO numberWhat is an IMO number?
9321196
MMSIWhat is an MMSI?
636026392
Call signWhat is a call sign?
A8TP2
AIS ship type
Tanker
Gross tonnageGross tonnage vs deadweight
40,953
Length overall
228 m
Beam
32.3 m
Year built
2007

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, 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.

DateEventSource
Left KeppelAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at KeppelAIS-detectedVoydar port-call detector (AIS geofence)
Left Tanjung PelepasAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Tanjung PelepasAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from New YorkAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at New YorkAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from PAULSBORO, NJAuthority-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
20257,385 t2,336 t84 days386 kg

Technical efficiency: EEXI (4.07 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
Keppel SGKEPSep 26, 2026, 01:23 UTCSep 26, 2026, 02:29 UTC1 h 6 min
Tanjung Pelepas MYTPPSep 24, 2026, 04:53 UTCSep 26, 2026, 00:18 UTC43 h 26 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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
New York USNYCDepartureJul 25, 2014(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalJul 25, 2014(date only)—USACE foreign traffic vessel entrances & clearances
PAULSBORO, NJDepartureJul 23, 2014(date only)—USACE foreign traffic vessel entrances & clearances
PAULSBORO, NJDepartureJul 22, 2014(date only)—USACE foreign traffic vessel entrances & clearances
PAULSBORO, NJArrivalJul 21, 2014(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCDepartureApr 23, 2014(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalApr 22, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Port Arthur USPOADepartureNov 5, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Port Arthur USPOAArrivalNov 3, 2013(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureAug 14, 2013(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)ArrivalAug 13, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Texas City USTXTDepartureAug 9, 2013(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: October 16, 2007.

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.

WhenWhat we observedConfidence
Sep 26, 2026, 00:52 UTC
Draught change

Reported draught went from 10.7 m to 12 m after leaving Tanjung Pelepas. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)

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 GISELE now?
GISELE (Oil tanker, Liberia flag) was last seen on AIS on Sep 29, 2026, 00:53 UTC, under way at 12.8 kn, in the Java Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
What kind of ship is GISELE?
GISELE is an oil tanker sailing under the flag of Liberia, built in 2007 by Minaminippon Shipbuilding. The vessel is 228 m long with a beam of 32.3 m and has a gross tonnage of 40,953.
Who is recorded as the owner or manager of GISELE?
Fleet Management Limited is recorded as ISM manager for GISELE (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for GISELE?
Voydar has no matched sanctions record displayed for GISELE 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 GISELE. 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/9321196
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