SOLITAIRE I
General cargo ship · Panama · built 2000 · AIS Class A
In short
SOLITAIRE I (General cargo ship, Panama flag) was last seen on AIS on , at anchor, in the Baltic Sea. Its crew-entered AIS destination is ST PETERBURG RUSSIA; its reported draught is 5.6 m (voyage report via Digitraffic marine AIS, received Nov 16, 2026, 03:11 UTC). ISM manager: SUNBERRY OCEANWAYS LTD. (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
Current voyage: from Kakumae (departed Nov 13, 2026, 18:23 UTC) to ST PETERBURG RUSSIA
- Vessel type
- General cargo ship
- Flag
- Panama
- Year built
- 2000
- Gross tonnage
- 15,609
- Size (length × beam)
- 160 m
- ISM manager
- SUNBERRY OCEANWAYS LTD.

Last reported position: 60.0906° N, 29.4125° E · Baltic Sea · See on the map
Watch this ship
Get an email when SOLITAIRE I 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
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 16, 2026, 15:59 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for SOLITAIRE I 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
- 60.0906° N, 29.4125° E
- Area
- Baltic Sea
- Status
- At anchorWhat do AIS statuses mean?
- Speed
- 0.6 kn
- Course
- —
- Heading
- 196°
- Compass: heading 196°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 3 port calls (Kakumae, Saint Petersburg (ex Leningrad), and Skagen).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows SOLITAIRE I's track before the last 30 days. Voydar has recorded its port calls since July 2, 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 160 mone tick every 25 m
- Name
- SOLITAIRE I
- IMO numberWhat is an IMO number?
- 9227962
- MMSIWhat is an MMSI?
- 353047000
- Call signWhat is a call sign?
- H3FH
- Flag
- Panama
- Gross tonnageGross tonnage vs deadweight
- 15,609
- Length overall
- 160 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via Digitraffic marine AIS on November 16, 2026.26 m
- Year built
- 2000
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 Digitraffic marine AIS on November 16, 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 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 |
|---|---|---|
| Left KakumaeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KakumaeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Saint Petersburg (ex Leningrad)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Saint Petersburg (ex Leningrad)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SkagenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SkagenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from PortlandAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at PortlandAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from LongviewAuthority-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.
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 Feb 18, 2012乗揚 · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)長崎県壱岐市若宮島北方沖 壱岐市所在の若宮灯台から真方位331°560m付近
貨物船SEA BELL乗揚Report published May 31, 2013
本船は、船長、二等航海士ほか17人が乗り組み、関門港の入港日時を調整するため、対馬海峡で漂泊を開始し、その後、機関を使って船位を2回修正したのち、平成24年2月17日19時00分ごろ若宮島西北西方沖約30kmの所で再び漂泊を開始した。 本船は、海流と風により東方に圧流される状況下、二等航海士が、18日00時00分ごろ船橋当直に就いたが、00時15分ごろ天気図を受信するためにファックスを操作し、椅子に腰を掛けて受信終了を待っている間に居眠りに陥った。 本船は、01時00分過ぎごろから南東方から南方に圧流されるようになり、二等航海士が、海上保安庁からの国際VHF無線電話による呼び掛けにより目覚めて応答し、自船の喫水などを連絡した直後、03時30分ごろ若宮島北方沖の浅所に乗り揚げた。 本船は、船長が、本事故発生後に昇橋し、機関を使って離礁を試みたものの、離礁することができなかったので、両舷錨を使
Source: 運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports). 出典:運輸安全委員会「船舶事故等調査報告書」(https://jtsb.mlit.go.jp/)。Seadar が項目を抽出・加工して作成 (Source: Japan Transport Safety Board marine accident reports; fields extracted and edited by Seadar). Licence: Public Data License 1.0 (公共データ利用規約 第1.0版, PDL1.0; compatible with CC BY 4.0).
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 | 5,645 t | 1,791 t | 108 days | 276 kg |
| 2019 | 7,476 t | 2,373 t | 139 days | 233 kg |
| 2020 | 5,896 t | 1,863 t | 116 days | 212 kg |
| 2021 | 5,947 t | 1,890 t | 123 days | 196 kg |
| 2022 | 2,530 t | 803 t | 52 days | 197 kg |
| 2023 | 2,957 t | 939 t | 55 days | 199 kg |
| 2024 | 5,327 t | 1,696 t | 108 days | 198 kg |
| 2025 | 2,109 t | 674 t | 42 days | 220 kg |
Technical efficiency: EEXI (7.55 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 “General cargo ship”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile11.87 g per tonne-nautical mile
- Lowest reportedHighest reported
7% of the 661 ships in this group reported a lower figure.
Group: lower quartile 23.23 · median 30.36 · upper quartile 42.59
- CO₂ per nautical mile sailed220 kg per nautical mile
- Lowest reportedHighest reported
84% of the 2,956 ships in this group reported a lower figure.
Group: lower quartile 74.8 · median 110.6 · upper quartile 185.8
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 |
|---|---|---|---|
| Kakumae EEKAK | Nov 13, 2026, 14:20 UTC | Nov 13, 2026, 18:23 UTC | 4 h 3 min |
| Saint Petersburg (ex Leningrad) RULED | Oct 29, 2026, 06:53 UTC | Oct 29, 2026, 18:11 UTC | 11 h 18 min |
| Skagen DKSKA | Oct 22, 2026, 23:03 UTC | Oct 23, 2026, 07:06 UTC | 8 h 2 min |
| Carenage TTCRN | Jul 2, 2026, 18:13 UTC | Jul 9, 2026, 18:22 UTC | 7 d 0 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 |
|---|---|---|---|---|
| Portland USPDX | Departure | Jun 21, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Arrival | Jun 13, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Longview USLOG | Departure | Jan 18, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Astoria USAST | Arrival | Jan 5, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Vancouver USVAN | Departure | Nov 16, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Vancouver USVAN | Arrival | Nov 11, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Honolulu USHNL | Departure | Nov 1, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Honolulu USHNL | Arrival | Oct 29, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Oct 9, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Arrival | Oct 7, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Richmond USRCH | Departure | Jan 18, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Richmond USRCH | Arrival | Jan 17, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: January 28, 2002.
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 SOLITAIRE I?
- SOLITAIRE I is a general cargo ship sailing under the flag of Panama, built in 2000 by Iwagi Zosen. The vessel is 160 m long and has a gross tonnage of 15,609.
- Who is recorded as the owner or manager of SOLITAIRE I?
- SUNBERRY OCEANWAYS LTD. is recorded as ISM manager for SOLITAIRE I (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for SOLITAIRE I?
- Voydar has no matched sanctions record displayed for SOLITAIRE I 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 SOLITAIRE I. 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/9227962Cite this page
SOLITAIRE I. Voydar (voydar.com). https://www.voydar.com/vessel/9227962-solitaire-i. Retrieved November 16, 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 adds internal business use; API plans add building the data into your own products.