Where is JBU Opal now?

Voydar has no displayable AIS position for JBU Opal in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.

What kind of ship is JBU Opal?

JBU Opal is a chemical tanker, built in 2009 by Kitanihon Shipbuilding. The vessel is 141 m long with a beam of 24.2 m and has a gross tonnage of 11,561.

Who is recorded as the owner or manager of JBU Opal?

(주)타이쿤쉽핑 is recorded as Registered owner for JBU Opal (source: 해양수산부 국제선박등록정보 (Korean International Ship Register)). This source record does not independently confirm today’s ownership or management.

What sanctions and inspection records does Voydar hold for JBU Opal?

Voydar has no matched sanctions record displayed for JBU Opal 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 JBU Opal. Missing records do not establish whether the ship has been detained.

JBU Opal

Chemical tanker · built 2009

IMO9400409No AIS position on record

Open in Terminal

In short

JBU Opal (Chemical tanker) has no AIS position on record with Voydar. Registered owner: (주)타이쿤쉽핑 (source: 해양수산부 국제선박등록정보 (Korean International Ship Register)).

Vessel type: Chemical tanker
Flag: —
Year built: 2009
Gross tonnage: 11,561
Size (length × beam): 141 m × 24 m
Registered owner: (주)타이쿤쉽핑

Watch this ship

Get an email when JBU Opal 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 JBU Opal.

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

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: JBU Opal
IMO numberWhat is an IMO number?: 9400409
MMSIWhat is an MMSI?: —
Call signWhat is a call sign?: —
Flag: —
Vessel type: Detailed type from EU MRV (THETIS-MRV) emissionsChemical tanker
Gross tonnageGross tonnage vs deadweight: 11,561
Deadweight (DWT): Source: Wikidata, record Q85981143. Added to Voydar on September 23, 2026. Licence: CC0 1.0.19,864 t
Length overall: 141 m
Beam: 24.2 m
Year built: 2009

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.

Registered owner: (주)타이쿤쉽핑(not linked to a company record)
Source: 해양수산부 국제선박등록정보 (Korean International Ship Register) · reported · confidence 0.9 · retrieved Sep 29, 2026
ISM manager: Taikun Shipping Co Ltd
Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 2026
Builder: Kitanihon Shipbuilding
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
키타니혼조선(주)(not linked to a company record)
Source: 해양수산부 국제선박등록정보 (Korean International Ship Register) · reported · confidence 0.9 · retrieved Sep 29, 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
Dec 22, 2016	Reported departure from HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported	USACE foreign traffic vessel entrances & clearances
Dec 20, 2016	Reported arrival at HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported	USACE foreign traffic vessel entrances & clearances
Dec 14, 2016	Reported departure from Lake CharlesAuthority-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
2021	2,355 t	743 t	31 days	280 kg
2024	1,828 t	577 t	20 days	355 kg
2025	0 t	0 t	0 days	—

Technical efficiency: EEXI (7.81 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
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Departure	Dec 22, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Arrival	Dec 20, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Lake Charles USLCH	Departure	Dec 14, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Lake Charles USLCH	Arrival	Dec 14, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Departure	Sep 1, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Arrival	Aug 28, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Lake Charles USLCH	Arrival	Aug 26, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Lake Charles USLCH	Departure	Aug 26, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Arrival	Aug 16, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Departure	Aug 16, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
New Orleans USMSY	Departure	Aug 13, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
New Orleans USMSY	Arrival	Aug 13, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances

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

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 JBU Opal now?: Voydar has no displayable AIS position for JBU Opal in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is JBU Opal?: JBU Opal is a chemical tanker, built in 2009 by Kitanihon Shipbuilding. The vessel is 141 m long with a beam of 24.2 m and has a gross tonnage of 11,561.
Who is recorded as the owner or manager of JBU Opal?: (주)타이쿤쉽핑 is recorded as Registered owner for JBU Opal (source: 해양수산부 국제선박등록정보 (Korean International Ship Register)). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for JBU Opal?: Voydar has no matched sanctions record displayed for JBU Opal 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 JBU Opal. 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/9400409

View JSON API documentationFree without a key for occasional use; use an API key for more.

Follow by RSS Open data

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