Torm Freya
Oil tanker · built 2003
In short
Torm Freya (Oil tanker) has no AIS position on record with Seadar.
- Vessel type
- Oil tanker
- Flag
- —
- Year built
- 2003
- Gross tonnage
- 30,128
- Size (length × beam)
- 183 m
- Registered owner
- —
Watch this ship
Get an email when Torm Freya 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 Torm Freya.
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
- Torm Freya
- IMO numberWhat is an IMO number?
- 9250490
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Gross tonnageGross tonnage vs deadweight
- 30,128
- Length overall
- 183 m
- Beam
- —
- Year built
- 2003
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.
No owner, operator or manager is recorded for this vessel yet.
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.
| 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 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 arrival at 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 |
|---|---|---|---|---|
| 2018 | 0 t | 0 t | 0 days | — |
| 2019 | 0 t | 0 t | 0 days | — |
Technical efficiency: EIV (6.18 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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | May 12, 2020, 10:55 UTC | PAFF | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jul 20, 2018, 07:30 UTC | TPGAS | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Lake Charles USLCH | Arrival | Sep 8, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Departure | Sep 8, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Sep 4, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Sep 2, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| NEW CASTLE AREA, DE | Departure | Jul 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Wilmington USILG | Arrival | Jul 21, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Haven USHVN | Departure | Jul 17, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Haven USHVN | Arrival | Jul 17, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PAULSBORO, NJ | Departure | Jul 4, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PAULSBORO, NJ | Arrival | Jul 4, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: May 31, 2003.
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 Torm Freya now?
- Seadar has no displayable AIS position for Torm Freya in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Torm Freya?
- Torm Freya is an oil tanker, built in 2003. The vessel is 183 m long and has a gross tonnage of 30,128.
- What sanctions and inspection records does Seadar hold for Torm Freya?
- Seadar has no matched sanctions record displayed for Torm Freya 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 Torm Freya. 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/9250490Using 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.