LNG Enugu
LNG carrier · Bermuda · built 2005 · AIS Class A
In short
LNG Enugu (LNG carrier, Bermuda flag) was last seen on AIS on , not moving, near Shekou Pt (South China 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 CN GSH; its reported draught is 9 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 07:13 UTC). ISM manager: BW Fleet Management AS (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- LNG carrier
- Flag
- Bermuda
- Year built
- 2005
- Gross tonnage
- 97,561
- Size (length × beam)
- 285 m × 43 m
- ISM manager
- BW Fleet Management AS
Watch this ship
LNG Enugu 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.
Free forever. No card. A free account follows up to 5 ships and ports.
Last reported position
received- Position
- 22.4965° N, 113.841° E
- Area
- South China Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 0 kn
- Course
- 277°
- Heading
- 133°
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)Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- LNG Enugu
- IMO numberWhat is an IMO number?
- 9266994
- MMSIWhat is an MMSI?
- 310482000
- Call signWhat is a call sign?
- ZCDM5
- Flag
- Bermuda
- Vessel type
- LNG carrier
- AIS ship type
- Tanker (hazardous cat. D)
- Gross tonnageGross tonnage vs deadweight
- 97,561
- Deadweight (DWT)
- Source: Wikidata, record Q117065671. Added to Voydar on September 23, 2026. Licence: CC0 1.0.83,068 t
- Length overall
- 285 m
- Beam
- 43 m
- Year built
- 2005
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 years 2024–2025 · reported · confidence 0.9 · retrieved Oct 5, 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 FreeportAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at FreeportAuthority-reported | USACE 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.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 27,723 t | 9,761 t | 112 days | 827 kg |
| 2019 | 44,068 t | 15,532 t | 148 days | 901 kg |
| 2020 | 33,973 t | 12,293 t | 175 days | 822 kg |
| 2021 | 35,967 t | 13,015 t | 175 days | 734 kg |
| 2022 | 22,156 t | 8,022 t | 120 days | 735 kg |
| 2023 | 19,738 t | 7,162 t | 97 days | 672 kg |
| 2024 | 20,623 t | 7,483 t | 145 days | 711 kg |
| 2025 | 11,900 t | 4,318 t | 54 days | 696 kg |
Technical efficiency: EEXI (7.33 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 | Sep 24, 2026, 01:17 UTC | SCCA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Freeport USFPO | Departure | Jul 12, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Freeport USFPO | Arrival | Jul 12, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CALVERT COUNTY, MARYLAND COVE POINT TO HOLLAND POINT, MD | Departure | Aug 30, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CALVERT COUNTY, MARYLAND COVE POINT TO HOLLAND POINT, MD | Arrival | Aug 30, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Departure | Jul 29, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Arrival | Jul 29, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Departure | May 2, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Arrival | May 1, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Departure | Dec 18, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Arrival | Dec 17, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Departure | Aug 9, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: April 4, 2006.
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 LNG Enugu now?
- LNG Enugu (LNG carrier, Bermuda flag) was last seen on AIS on Oct 1, 2026, 07:36 UTC, not moving, near Shekou Pt (South China 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 CN GSH (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 07:13 UTC). This report does not confirm the ship’s current route.
- What kind of ship is LNG Enugu?
- LNG Enugu is an LNG carrier sailing under the flag of Bermuda, built in 2005 by Hanwha Ocean. The vessel is 285 m long with a beam of 43 m and has a gross tonnage of 97,561.
- Who is recorded as the owner or manager of LNG Enugu?
- BW Fleet Management AS is recorded as ISM manager for LNG Enugu (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for LNG Enugu?
- Voydar has no matched sanctions record displayed for LNG Enugu 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 LNG Enugu. 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/9266994Using 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.