TORM CORRIDO
Chemical tanker · Denmark · built 2011 · AIS Class A
In short
TORM CORRIDO (Chemical tanker, Denmark flag) was last seen on AIS on , moored, near Tilbury (North Sea). Its crew-entered AIS destination is MARGATE, with an ETA of Oct 3, 2026, 17:00 UTC; its reported draught is 8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 12:56 UTC). ISM manager: TORM A/S (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from IJmuiden/Velsen (departed Sep 30, 2026, 19:15 UTC) to MARGATE
- Vessel type
- Chemical tanker
- Flag
- Denmark
- Year built
- 2011
- Gross tonnage
- 27,095
- Size (length × beam)
- 183 m × 32 m
- ISM manager
- TORM A/S
Watch this ship
Get an email when TORM CORRIDO 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 CORRIDO.
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
received- Position
- 51.463° N, 0.2676° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0.4 kn
- Course
- 226°
- Heading
- 303°
Last 30 days: 2 port calls (IJmuiden/Velsen).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls 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 CORRIDO
- IMO numberWhat is an IMO number?
- 9411305
- MMSIWhat is an MMSI?
- 219028420
- Call signWhat is a call sign?
- OZNT2
- Flag
- Denmark
- AIS ship type
- Tanker (hazardous cat. C)
- Gross tonnageGross tonnage vs deadweight
- 27,095
- Deadweight (DWT)
- Source: Wikidata, record Q84228748. Added to Voydar on September 23, 2026. Licence: CC0 1.0.46,156 t
- Length overall
- 182.9 m
- Beam
- 32.2 m
- Year built
- 2011
DenmarkA 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 Sep 28, 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 |
|---|---|---|
| Left IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| 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 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) |
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 | 13,076 t | 4,170 t | 145 days | 323 kg |
| 2020 | 12,247 t | 3,894 t | 161 days | 279 kg |
| 2021 | 2,417 t | 775 t | 29 days | 281 kg |
| 2022 | 7,042 t | 2,248 t | 71 days | 324 kg |
| 2023 | 7,569 t | 2,410 t | 87 days | 291 kg |
| 2024 | 5,820 t | 1,856 t | 62 days | 297 kg |
| 2025 | 0 t | 0 t | 0 days | — |
Technical efficiency: EEXI (5.15 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.
Detected from AIS AIS-detected
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| IJmuiden/Velsen NLIJM | Sep 30, 2026, 18:12 UTC | Sep 30, 2026, 19:15 UTC | 1 h 3 min |
| IJmuiden/Velsen NLIJM | Sep 27, 2026, 13:56 UTC | Sep 27, 2026, 14:44 UTC | 48 min |
Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival(matched by call sign) | Jun 9, 2026, 11:36 UTC | SLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jul 31, 2025, 09:19 UTC | SINO | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jul 21, 2025, 02:32 UTC | CTX | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jun 7, 2025, 08:08 UTC | SHELL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Dec 31, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Arrival | Dec 31, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Departure | Dec 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Arrival | Dec 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Arrival | Dec 2, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Departure | Dec 2, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Nov 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Nov 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: August 13, 2011.
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.
Behaviour at sea Voydar-derived
Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.
Predicted arrival
Voydar estimates arrival at Amsterdam around Oct 5, 2026, 06:28 UTC, most likely between Oct 1, 2026, 08:48 UTC and Oct 27, 2026, 07:04 UTC. Based on 59 past transits between NLIJM and Amsterdam seen in our port calls. The crew-reported ETA is Sep 27, 2026, 12:00 UTC.
Medium (53%) · Method seadar.behaviour.eta_prediction v1
| When | What we observed | Confidence |
|---|---|---|
| Oct 1, 2026, 03:02 UTC | Draught change Reported draught went from 8.6 m to 10.2 m after leaving IJmuiden/Velsen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.
Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.
Frequently asked questions
- Where is TORM CORRIDO now?
- TORM CORRIDO (Chemical tanker, Denmark flag) was last seen on AIS on Oct 3, 2026, 13:22 UTC, moored, near Tilbury (North Sea). The crew-entered destination was MARGATE (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 12:56 UTC). This report does not confirm the ship’s current route.
- What kind of ship is TORM CORRIDO?
- TORM CORRIDO is a chemical tanker sailing under the flag of Denmark, built in 2011. The vessel is 182.9 m long with a beam of 32.2 m and has a gross tonnage of 27,095.
- Who is recorded as the owner or manager of TORM CORRIDO?
- TORM A/S is recorded as ISM manager for TORM CORRIDO (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 TORM CORRIDO?
- Voydar has no matched sanctions record displayed for TORM CORRIDO 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 TORM CORRIDO. Missing records do not establish whether the ship has been detained.
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/9411305Using 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.