Skip to content

Fuji Lng

LNG carrier · built 2004

IMO9275359No AIS position on record

In short

Fuji Lng (LNG carrier) has no AIS position on record with Seadar. ISM manager: TMS Cardiff Gas Ltd. (source: EU MRV (THETIS-MRV) emissions, reporting year 2024).

Vessel type
LNG carrier
Flag
—
Year built
2004
Gross tonnage
118,219
Size (length × beam)
289 m

Watch this ship

Get an email when Fuji Lng 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 Fuji Lng.

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 Fuji Lng
Photo: Ken Hodge · Licence: CC BY 2.0 · via Wikimedia Commons

Last reported position

No AIS position on record for this vessel. Identity and particulars are 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
Fuji Lng
IMO numberWhat is an IMO number?
9275359
Flag
—
Vessel type
LNG carrier
Gross tonnageGross tonnage vs deadweight
118,219
Length overall
289 m
Beam
—
Year built
2004

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
Builder
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026

Timeline

Dated events for this ship from every source Seadar holds, newest first. Each line names its source; derived items say how they were derived.

DateEventSource
Reported departure from Lake CharlesAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at Lake CharlesAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from Lake CharlesAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Former name: Muscat LngWikidata

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.

Former and other names

Names attested for this ship other than its current name.

NameEvidenceDateSource
Muscat LngFormer nameJan 1, 2004Wikidata

A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Seadar saw them.

Source: Wikidata. Licence: CC0 1.0.

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
201922,129 t7,899 t97 days848 kg
20208,692 t3,044 t28 days842 kg
202215,693 t5,246 t41 days1,119 kg
202338,406 t13,688 t132 days932 kg
20247,396 t2,524 t15 days1,297 kg

Technical efficiency: EEXI (7.6 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 Seadar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Lake Charles USLCHDepartureDec 10, 2004(date only)—USACE foreign traffic vessel entrances & clearances
Lake Charles USLCHArrivalDec 9, 2004(date only)—USACE foreign traffic vessel entrances & clearances
Lake Charles USLCHDepartureJul 22, 2004(date only)—USACE foreign traffic vessel entrances & clearances
Lake Charles USLCHArrivalJul 21, 2004(date only)—USACE foreign traffic vessel entrances & clearances
Lake Charles USLCHDepartureMay 26, 2004(date only)—USACE foreign traffic vessel entrances & clearances
Lake Charles USLCHArrivalMay 26, 2004(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: May 26, 2004.

Frequently asked questions

Where is Fuji Lng now?
Seadar has no displayable AIS position for Fuji Lng in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Fuji Lng?
Fuji Lng is an LNG carrier, built in 2004 by Kawasaki Heavy Industries Ship & Offshore Structure Company. The vessel is 289 m long and has a gross tonnage of 118,219.
Who is recorded as the owner or manager of Fuji Lng?
TMS Cardiff Gas Ltd. is recorded as ISM manager for Fuji Lng (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 Seadar hold for Fuji Lng?
Seadar has no matched sanctions record displayed for Fuji Lng 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 Fuji Lng. 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/9275359
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