ORLANDO
Chemical tanker · Liberia · built 2009 · AIS Class A
In short
ORLANDO (Chemical tanker, Liberia flag) was last seen on AIS on , moored, in the port of Koper. Its crew-entered AIS destination is SI KOP (Koper), with an ETA of Nov 18, 2026, 10:00 UTC; its reported draught is 9.7 m (voyage report via AISstream.io global terrestrial AIS, received Nov 18, 2026, 13:41 UTC). It arrived there on Nov 18, 2026, 06:29 UTC. ISM manager: IMS S.A. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Chemical tanker
- Flag
- Liberia
- Year built
- 2009
- Gross tonnage
- 24,066
- Size (length × beam)
- 183 m × 27 m
- ISM manager
- IMS S.A.
Last reported position: 45.5589° N, 13.7346° E · Mediterranean Sea · See on the map
Watch this ship
Get an email when ORLANDO arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
What you would have been told
Following ORLANDO over the last 24 hours would have sent 1 message.
- ArrivedKoper
Detected from AIS, as of Nov 18, 2026, 19:40 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for ORLANDO reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans
Get alerts on your phone: Voydar for iPhone
Last reported position
received- Position
- 45.5589° N, 13.7346° E
- Area
- Mediterranean Sea
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 69°
- Heading
- 269°
- Compass: course over ground 69°, heading 269°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 2 port calls (Koper and Eleusina).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows ORLANDO's track before the last 30 days. Voydar has recorded its port calls since September 24, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 183 mone tick every 25 m
Beam 27.4 mPlan outline, to scale
- Name
- ORLANDO
- IMO numberWhat is an IMO number?
- 9420851
- MMSIWhat is an MMSI?
- 636022949
- Call signWhat is a call sign?
- A8RQ9
- Flag
- Liberia
- Gross tonnageGross tonnage vs deadweight
- 24,066
- Deadweight (DWT)
- Source: Wikidata, record Q85987104. Added to Voydar on October 26, 2026. Licence: CC0 1.0.38,334 t
- Length overall
- 183 m
- Beam
- 27.4 m
- Year built
- 2009
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 · high confidence · retrieved Nov 16, 2026
- Builder
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026
Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →
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 |
|---|---|---|
| Arrived at KoperAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left EleusinaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at EleusinaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left VlaardingenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at VlaardingenAIS-detected | Voydar port-call detector (AIS geofence) | |
| 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 HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-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 | 4,403 t | 1,408 t | 64 days | 353 kg |
| 2019 | 7,270 t | 2,320 t | 109 days | 353 kg |
| 2020 | 13,253 t | 4,210 t | 144 days | 317 kg |
| 2021 | 7,085 t | 2,246 t | 91 days | 281 kg |
| 2022 | 12,474 t | 3,975 t | 118 days | 361 kg |
| 2023 | 7,382 t | 2,329 t | 69 days | 371 kg |
| 2024 | 4,610 t | 1,469 t | 40 days | 413 kg |
| 2025 | 3,369 t | 1,060 t | 50 days | 293 kg |
Technical efficiency: EEXI (5.65 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
Compared with ships of its type
Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “Chemical tanker”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile15.2 g per tonne-nautical mile
- Lowest reportedHighest reported
51% of the 1,489 ships in this group reported a lower figure.
Group: lower quartile 10.24 · median 15.04 · upper quartile 25.97
- CO₂ per nautical mile sailed293.5 kg per nautical mile
- Lowest reportedHighest reported
72% of the 1,516 ships in this group reported a lower figure.
Group: lower quartile 203.4 · median 250.2 · upper quartile 301
Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated
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 |
|---|---|---|---|
| Koper SIKOP | Nov 18, 2026, 06:29 UTC | in port | — |
| Eleusina GREEU | Oct 24, 2026, 06:29 UTC | Oct 27, 2026, 19:25 UTC | 3 d 12 h |
| Vlaardingen NLVLA | Oct 2, 2026, 17:25 UTC | Oct 4, 2026, 13:15 UTC | 43 h 50 min |
| Algeciras ESALG | Sep 24, 2026, 09:42 UTC | Sep 24, 2026, 20:34 UTC | 10 h 53 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 |
|---|---|---|---|---|
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Nov 16, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Nov 15, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Oct 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Oct 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Sep 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Sep 13, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Aug 6, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Aug 6, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Arrival | Jul 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Departure | Jul 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Jul 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Jul 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: October 27, 2011.
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.
| When | What we observed | Confidence |
|---|---|---|
| Oct 27, 2026, 16:18 UTC | Draught change Reported draught went from 7 m to 10.2 m while in port at Eleusina. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 24, 2026, 06:42 UTC | Draught change Reported draught went from 8.2 m to 7 m while in port at Eleusina. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 4, 2026, 13:31 UTC | Draught change Reported draught went from 7.2 m to 10.7 m after leaving Vlaardingen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
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
- What kind of ship is ORLANDO?
- ORLANDO is a chemical tanker sailing under the flag of Liberia, built in 2009 by CSSC Offshore & Marine Engineering Company. The vessel is 183 m long with a beam of 27.4 m and has a gross tonnage of 24,066.
- Who is recorded as the owner or manager of ORLANDO?
- IMS S.A. is recorded as ISM manager for ORLANDO (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 ORLANDO?
- Voydar has no matched sanctions record displayed for ORLANDO 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 ORLANDO. Missing records do not establish whether the ship has been detained.
Full Vessel Report
A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.
Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.
Every fact on this page stays free.
Know this ship?
Help other readers. Member posts are shown as member content, never as sourced data.
- Date, place and an optional note
- Members who know her can answer
- Suggest a correctionChecked against sources before anything changes
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/9420851Cite this page
ORLANDO. Voydar (voydar.com). https://www.voydar.com/vessel/9420851-orlando. Retrieved November 18, 2026.
Each fact above names its own source and date. Cite that primary source too when you rely on a fact.
Using this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.