Skip to content

Team Adventurer

Chemical tanker · built 2007

IMO9326914No AIS position on record

In short

Team Adventurer (Chemical tanker) has no AIS position on record with Voydar. ISM manager: TORM A/S (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Chemical tanker
Flag
—
Year built
2007
Gross tonnage
26,751
Size (length × beam)
—
ISM manager
TORM A/S

Watch this ship

Team Adventurer 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.

Photo of Team Adventurer
Photo: Alf van Beem · Licence: Public domain · 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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
Team Adventurer
IMO numberWhat is an IMO number?
9326914
Flag
—
Gross tonnageGross tonnage vs deadweight
26,751
Length overall
—
Beam
—
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 years 2024–2025 · reported · confidence 0.9 · retrieved Oct 5, 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
Reported departure from Texas CityAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from PORT OF SOUTH LOUISIANA (LA)Authority-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
20185,593 t1,791 t49 days399 kg
20195,147 t1,641 t62 days307 kg
20207,060 t2,223 t77 days347 kg
20214,380 t1,392 t59 days360 kg
20223,254 t1,041 t34 days294 kg
20235,222 t1,666 t57 days289 kg
20246,120 t1,947 t75 days262 kg
20256,121 t1,972 t78 days264 kg

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

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Texas City USTXTDepartureSep 2, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalAug 26, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureAug 19, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LAArrivalAug 18, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureJun 29, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPArrivalJun 27, 2016(date only)—USACE foreign traffic vessel entrances & clearances
YABUCOA HARBOR, PRDepartureJun 20, 2016(date only)—USACE foreign traffic vessel entrances & clearances
YABUCOA HARBOR, PRArrivalJun 19, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureMay 2, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalApr 26, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Beaumont USBPTDepartureApr 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Beaumont USBPTArrivalApr 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is Team Adventurer now?
Voydar has no displayable AIS position for Team Adventurer in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Team Adventurer?
Team Adventurer is a chemical tanker, built in 2007. The vessel has a gross tonnage of 26,751.
Who is recorded as the owner or manager of Team Adventurer?
TORM A/S is recorded as ISM manager for Team Adventurer (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 Team Adventurer?
Voydar has no matched sanctions record displayed for Team Adventurer 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 Team Adventurer. 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/9326914
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