Adatrans
General cargo ship · built 2001
In short
Adatrans (General cargo ship) has no AIS position on record with Voydar.
- Vessel type
- General cargo ship
- Flag
- —
- Year built
- 2001
- Gross tonnage
- 6,167
- Size (length × beam)
- 131 m
- Registered owner
- —
Watch this ship
Get an email when Adatrans 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 Adatrans.
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-upIdentity & particulars
- Name
- Adatrans
- IMO numberWhat is an IMO number?
- 9037276
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Gross tonnageGross tonnage vs deadweight
- 6,167
- Length overall
- 130.8 m
- Beam
- —
- Year built
- 2001
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.
- 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 HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from Panama CityAuthority-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 |
|---|---|---|---|---|
| 2019 | 4,311 t | 1,365 t | 136 days | 138 kg |
| 2020 | 3,132 t | 985 t | 128 days | 153 kg |
| 2021 | 570 t | 178 t | 241 days | 530 kg |
Technical efficiency: EIV (14.25 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 | Feb 20, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Feb 17, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Panama City USPFN | Departure | Sep 25, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Panama City USPFN | Arrival | Sep 25, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Departure | Jul 30, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Arrival | Jul 21, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| FERNANDINA HARBOR, FL | Departure | Apr 7, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| FERNANDINA HARBOR, FL | Arrival | Apr 6, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Departure | Apr 2, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Arrival | Apr 2, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Tampa USTPA | Departure | Mar 8, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Tampa USTPA | Arrival | Mar 5, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: February 2, 2002.
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 Adatrans now?
- Voydar has no displayable AIS position for Adatrans in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Adatrans?
- Adatrans is a general cargo ship, built in 2001 by Torgem Shipyard. The vessel is 130.8 m long and has a gross tonnage of 6,167.
- What sanctions and inspection records does Voydar hold for Adatrans?
- Voydar has no matched sanctions record displayed for Adatrans 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 Adatrans. 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/9037276Using 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.