Torx appears on the UK Sanctions List, the New Zealand Russia Sanctions Register, the EU list of designated vessels and the Canadian autonomous sanctions list under Russia, Russia Sanctions Act 2022 (New Zealand), Russia (Reg. 833/2014 Annex XLII). Verify at GOV.UK.
Every vessel on:UK Sanctions ListNew Zealand Russia Sanctions RegisterEU list of designated vesselsCanadian autonomous sanctions list
Torx
Oil tanker · built 2006
In short
Torx (Oil tanker) has no AIS position on record with Voydar. It appears on 4 sanctions lists (details below).
- Vessel type
- Oil tanker
- Flag
- —
- Year built
- 2006
- Gross tonnage
- 87,146
- Size (length × beam)
- 281 m
- Registered owner
- —
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
- Torx
- IMO numberWhat is an IMO number?
- 9311610
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Gross tonnageGross tonnage vs deadweight
- 87,146
- Length overall
- 281 m
- Beam
- —
- Year built
- 2006
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.
- Owner or operator (sanctions listing)
- Shiva Shipping Ltd(not linked to a company record)Source: UK Sanctions List (FCDO) · reported · confidence 0.7 · retrieved Oct 2, 2026
- 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 |
|---|---|---|
| Listed on the Canadian autonomous sanctions list (Russia) | Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA) | |
| Listed on the New Zealand Russia Sanctions Register (MFAT) (Russia Sanctions Act 2022 (New Zealand)) | New Zealand Russia Sanctions Register (ships) | |
| Listed on the EU designated vessels (Official Journal) (Russia (Reg. 833/2014 Annex XLII)) | EU designated vessels (Reg. 833/2014 Annex XLII; Reg. 2017/1509 Annex XIV) | |
| Listed on the UK Sanctions List (Russia) | UK Sanctions List (FCDO) | |
| 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 ANACORTES HARBOR, WAAuthority-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.
Sanctions listings
Every listing of this ship on the sanctions lists Voydar tracks, current and past.
| List | Programme | Listed as | Listed | Status |
|---|---|---|---|---|
| Canadian autonomous sanctions list | Russia | Torx | Mar 25, 2026 | In force |
| New Zealand Russia Sanctions Register (MFAT) | Russia Sanctions Act 2022 (New Zealand) | Torx | Feb 20, 2026 | In force |
| EU designated vessels (Official Journal) | Russia (Reg. 833/2014 Annex XLII) | Torx | Oct 24, 2025 | In force |
| UK Sanctions List | Russia | TORX | Oct 15, 2025 | In force |
Source: Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA). Contains information licensed under the Open Government Licence – Canada. Licence: Open Government Licence – Canada.
Source: New Zealand Russia Sanctions Register (ships). © Crown copyright, New Zealand Ministry of Foreign Affairs and Trade, CC BY 4.0. Licence: CC-BY-4.0 (Crown copyright).
Source: Council Regulation (EU) No 833/2014, Annex XLII, and Council Regulation (EU) 2017/1509, Annex XIV (Official Journal of the European Union); list compiled by the Danish Maritime Authority. Licence: EU legislation (Official Journal): reuse "for commercial or non-commercial purposes" (Decision 2011/833/EU); facts.
Source: UK Sanctions List (FCDO). Contains public sector information licensed under the Open Government Licence v3.0. Licence: OGL v3.
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 | 19,525 t | 6,219 t | 101 days | 695 kg |
| 2019 | 16,064 t | 5,130 t | 95 days | 727 kg |
| 2020 | 19,944 t | 6,315 t | 101 days | 734 kg |
Technical efficiency: EIV (4.05 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 | May 2, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | May 2, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ANACORTES HARBOR, WA | Departure | Jan 14, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ANACORTES HARBOR, WA | Arrival | Oct 1, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| OTHER PUGET SOUND AREA PORTS, WA (NET) | Departure | Sep 13, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| OTHER PUGET SOUND AREA PORTS, WA (NET) | Arrival | Sep 3, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Feb 15, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Feb 11, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CARQUINEZ STRAIT, CA | Departure | Jan 5, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CARQUINEZ STRAIT, CA | Arrival | Jan 3, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CARQUINEZ STRAIT, CA | Departure | Oct 22, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CARQUINEZ STRAIT, CA | Arrival | Oct 21, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: October 10, 2006.
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 Torx now?
- Voydar has no displayable AIS position for Torx in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Torx?
- Torx is an oil tanker, built in 2006 by Hanwha Ocean. The vessel is 281 m long and has a gross tonnage of 87,146.
- What sanctions and inspection records does Voydar hold for Torx?
- Torx appears on the UK Sanctions List, the New Zealand Russia Sanctions Register, the EU list of designated vessels and the Canadian autonomous sanctions list under Russia, Russia Sanctions Act 2022 (New Zealand), Russia (Reg. 833/2014 Annex XLII). No matched inspection records are displayed for Torx. 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/9311610Using 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.