Sirius 1 appears on the UK Sanctions List, the EU list of designated vessels, the Canadian autonomous sanctions list and the OFAC SDN list under the Russia, Russia (Reg. 833/2014 Annex XLII), UKRAINE-EO13662, and RUSSIA-EO14024 programs. Verify at GOV.UK.
Every vessel on:UK Sanctions ListEU list of designated vesselsCanadian autonomous sanctions listOFAC SDN list
Sirius 1
Oil tanker · Mali · built 2005 · AIS Class B
In short
Sirius 1 (Oil tanker, Mali flag) was last seen on AIS on , under way at 9.5 kn, near As Suways (Suez) (Mediterranean Sea). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its last detected port call was at Hong Kong: arrived Oct 7, 2026, left Oct 10, 2026. ISM manager: CASTOR SHIPS S.A. (source: EU MRV (THETIS-MRV) emissions, reporting year 2024). It appears on 4 sanctions lists (details below).
- Vessel type
- Oil tanker
- Flag
- Mali
- Year built
- 2005
- Gross tonnage
- 62,806
- Size (length × beam)
- 250 m
- ISM manager
- CASTOR SHIPS S.A.

Last reported position: 30.1569° N, 32.5697° E · Mediterranean Sea · See on the map
Watch this ship
Sirius 1 has not been received for a while. Follow it for an email update when Voydar receives a new position, and for arrival and departure alerts.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 17, 2026, 17:15 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Sirius 1 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
- 30.1569° N, 32.5697° E
- Area
- Mediterranean Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 9.5 kn
- Course
- 359°
- Heading
- 358°
- Compass: course over ground 359°, heading 358°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Voydar detected no port call in the last 30 days.
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Sirius 1's track before the last 30 days. Voydar has recorded its port calls since October 7, 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 250 mone tick every 25 m
- Name
- Sirius 1
- IMO numberWhat is an IMO number?
- 9285847
- MMSIWhat is an MMSI?
- 649136000
- Call signWhat is a call sign?
- TZBJ1
- Flag
- Mali
- Gross tonnageGross tonnage vs deadweight
- 62,806
- Length overall
- 250 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on October 25, 2026.40 m
- Year built
- 2005
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.
AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via AISstream.io global terrestrial AIS on October 25, 2026.
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 year 2024 · reported · high confidence · retrieved Nov 16, 2026
- Owner or operator (sanctions listing)
- Estrella Co Ltd(not linked to a company record)Source: UK Sanctions List (FCDO) · reported · medium confidence · retrieved Nov 17, 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 |
|---|---|---|
| Left Hong KongAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Arrived at Hong KongAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Listed on the Canadian autonomous sanctions list (Russia) | Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA) | |
| Listed on the UK Sanctions List (Russia) | UK Sanctions List (FCDO) | |
| 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) | |
| Reported arrival at PAULSBORO, NJAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from PAULSBORO, NJAuthority-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.
Former and other names
Names attested for this ship other than its current name.
| Name | Evidence | Date | Source |
|---|---|---|---|
| Sirius I | Name on a sanctions list | — | EU designated vessels (Reg. 833/2014 Annex XLII; Reg. 2017/1509 Annex XIV) |
A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.
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.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred May 12, 2018ACC · Cargo, Liquid BulkNTSB marine investigations (CAROL)North Atlantic Ocean
Tofteviken / Polaris (NTSB DCA18FM023)Report published Jun 28, 2019
The National Transportation Safety Board determines that the probable cause of the collision between the fishing vessel Polaris and the tanker Tofteviken was the failure to maintain a proper lookout by the mate on the fishing vessel and the failure to identify the risk of collision by the third mate on the tanker.
Source: NTSB marine investigations (CAROL). Courtesy: National Transportation Safety Board. Licence: US Government work (17 U.S.C. §105), public domain.
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 | Sirius 1 | Nov 6, 2025 | In force |
| UK Sanctions List | Russia | SIRIUS 1 | Sep 12, 2025 | In force |
| EU designated vessels (Official Journal) | Russia (Reg. 833/2014 Annex XLII) | Sirius I | Jul 20, 2025 | In force |
| OFAC SDN list (US) | UKRAINE-EO13662, RUSSIA-EO14024 | SIRIUS 1 | not published by the list | 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: UK Sanctions List (FCDO). Contains public sector information licensed under the Open Government Licence v3.0. Licence: OGL v3.
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: OFAC Specially Designated Nationals list. Licence: US Government public domain (17 U.S.C. §105).
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 | 3,288 t | 1,048 t | 25 days | 535 kg |
| 2019 | 26,059 t | 8,271 t | 238 days | 558 kg |
| 2020 | 13,674 t | 4,276 t | 166 days | 548 kg |
| 2021 | 11,682 t | 3,714 t | 78 days | 632 kg |
| 2022 | 12,532 t | 4,005 t | 133 days | 417 kg |
| 2023 | 2,080 t | 664 t | 17 days | 1,138 kg |
| 2024 | 1,787 t | 571 t | 19 days | 491 kg |
Technical efficiency: EIV (3.67 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 2024 sits among the ships EU MRV lists as “Oil tanker”. Lower is less CO₂.
- CO₂ per nautical mile sailed490.8 kg per nautical mile
- Lowest reportedHighest reported
74% of the 1,917 ships in this group reported a lower figure.
Group: lower quartile 316.6 · median 406.3 · upper quartile 494.9
This ship’s 2024 figures were built from part-year reports, so the comparison does not describe a full year.
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 |
|---|---|---|---|
| Hong Kong HKHKG | Oct 7, 2026, 21:58 UTC | Oct 10, 2026, 05:32 UTC | 2 d 7 h |
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 | Oct 7, 2026, 07:22 UTC | SLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| PAULSBORO, NJ | Arrival | Dec 17, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PAULSBORO, NJ | Departure | Dec 17, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Departure | Dec 5, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Arrival | Dec 4, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Departure | Nov 25, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Arrival | Nov 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Texas City USTXT | Departure | Nov 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Texas City USTXT | Arrival | Nov 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Departure | Nov 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Arrival | Oct 31, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Departure | Oct 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: August 2, 2007.
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
- What kind of ship is Sirius 1?
- Sirius 1 is an oil tanker sailing under the flag of Mali, built in 2005 by Samsung Heavy Industries. The vessel is 250 m long and has a gross tonnage of 62,806.
- Who is recorded as the owner or manager of Sirius 1?
- CASTOR SHIPS S.A. is recorded as ISM manager for Sirius 1 (source: EU MRV (THETIS-MRV) emissions; reporting year 2024). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for Sirius 1?
- Sirius 1 appears on the UK Sanctions List, the EU list of designated vessels, the Canadian autonomous sanctions list and the OFAC SDN list under the Russia, Russia (Reg. 833/2014 Annex XLII), UKRAINE-EO13662, and RUSSIA-EO14024 programs. No matched inspection records are displayed for Sirius 1. 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/9285847Cite this page
Sirius 1. Voydar (voydar.com). https://www.voydar.com/vessel/9285847-sirius1. Retrieved November 17, 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.