OSLEEN
Bulk carrier · San Marino · built 2004 · AIS Class A
In short
OSLEEN (Bulk carrier, San Marino flag) was last seen on AIS on , under way at 2.9 kn, in the Baltic Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is RU ULU (Ust'-Luga); its reported draught is 8.6 m (voyage report via Digitraffic marine AIS, received Oct 3, 2026, 12:52 UTC). ISM manager: El Faro Shipping Ltd (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Bulk carrier
- Flag
- San Marino
- Year built
- 2004
- Gross tonnage
- 19,828
- Size (length × beam)
- 175 m
- ISM manager
- El Faro Shipping Ltd
Watch this ship
Get an email when OSLEEN 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 OSLEEN.
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
- 59.9806° N, 28.6142° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 2.9 kn
- Course
- 115°
- Heading
- 114°
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.
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
- OSLEEN
- IMO numberWhat is an IMO number?
- 9278739
- MMSIWhat is an MMSI?
- 268238202
- Call signWhat is a call sign?
- T7AG6
- Flag
- San Marino
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 19,828
- Length overall
- 174.7 m
- Beam
- —
- Year built
- 2004
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 · confidence 0.9 · retrieved Sep 28, 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 |
|---|---|---|
| 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) | |
| Port State Control inspection at Portland, Oregon | USCG PSIX / CGMIX inspections | |
| Reported departure from AstoriaAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Inspection at WASHINGTON, District of Columbia | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at San Francisco, California | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at North Charleston, South Carolina | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Portland, Oregon | USCG PSIX / CGMIX inspections | |
| Inspection at Portland, Oregon | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Portland, Oregon | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Portland, Oregon | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at San Pedro, California | USCG PSIX / CGMIX inspections |
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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Aug 19, 2014 | Vessel InspectionPSC | Portland, Oregon | clean |
| Aug 5, 2014 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Jul 30, 2014 | Vessel InspectionPSC | San Francisco, California | clean |
| Jul 29, 2013 | Vessel InspectionPSC | North Charleston, South Carolina | clean |
| Feb 24, 2011 | Vessel InspectionPSC | Portland, Oregon | clean |
| Feb 17, 2011 | Vessel Operational Control | Portland, Oregon | clean |
| Feb 26, 2010 | Vessel Inspection | Seattle, Washington | clean |
| Jun 10, 2009 | Vessel InspectionPSC | Portland, Oregon | clean |
| May 21, 2008 | Vessel InspectionPSC | Portland, Oregon | clean |
| Sep 29, 2006 | Vessel InspectionPSC | San Pedro, California | clean |
| Sep 25, 2006 | Boarding | San Pedro, California | clean |
| Sep 22, 2006 | Vessel Operational Control | San Pedro, California | clean |
| Sep 20, 2005 | Vessel InspectionPSC | New Orleans, Louisiana | clean |
| Jun 27, 2005 | Vessel InspectionPSC | Seattle, Washington | clean |
| Jun 15, 2005 | Vessel InspectionPSC | Portland, Oregon | clean |
| Jan 12, 2005 | Vessel InspectionPSC | San Pedro, California | clean |
| May 26, 2004 | Vessel InspectionPSC | Portland, Oregon | clean |
| May 25, 2004 | Boarding | Portland, Oregon | clean |
Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.
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 | — |
| 2022 | 1,231 t | 393 t | 20 days | 215 kg |
| 2024 | 4,598 t | 1,467 t | 80 days | 222 kg |
| 2025 | 5,858 t | 1,879 t | 95 days | 223 kg |
Technical efficiency: EEXI (5.32 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 |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | Jul 16, 2020, 04:57 UTC | NWLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Dec 31, 2018, 23:28 UTC | ELC | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Astoria USAST | Departure | Aug 19, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Astoria USAST | Arrival | Aug 8, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CARQUINEZ STRAIT, CA | Departure | Aug 4, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CARQUINEZ STRAIT, CA | Arrival | Jul 27, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Aug 24, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Aug 7, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Departure | Aug 1, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Arrival | Jul 26, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Feb 25, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Vancouver USVAN | Arrival | Feb 21, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: May 25, 2004.
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 OSLEEN now?
- OSLEEN (Bulk carrier, San Marino flag) was last seen on AIS on Oct 2, 2026, 17:59 UTC, under way at 2.9 kn, in the Baltic Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was RU ULU (voyage report via Digitraffic marine AIS, received Oct 3, 2026, 12:52 UTC). This report does not confirm the ship’s current route.
- What kind of ship is OSLEEN?
- OSLEEN is a bulk carrier sailing under the flag of San Marino, built in 2004 by Oshima Shipbuilding. The vessel is 174.7 m long and has a gross tonnage of 19,828.
- Who is recorded as the owner or manager of OSLEEN?
- El Faro Shipping Ltd is recorded as ISM manager for OSLEEN (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 OSLEEN?
- Voydar has no matched sanctions record displayed for OSLEEN 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. OSLEEN has 18 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
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/9278739Using 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.