River Pearl
General cargo ship · Bahamas · built 2008
In short
River Pearl (General cargo ship, Bahamas flag) has no AIS position on record with Voydar. ISM manager: SMT Shipping (Cyprus) Ltd (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- General cargo ship
- Flag
- Bahamas
- Year built
- 2008
- Gross tonnage
- 29,765
- Size (length × beam)
- 188 m × 32 m
- ISM manager
- SMT Shipping (Cyprus) Ltd
Watch this ship
Get an email when River Pearl 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 River Pearl.
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
No AIS position on record for this vessel. Identity and particulars are 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
- River Pearl
- IMO numberWhat is an IMO number?
- 9363663
- MMSIWhat is an MMSI?
- 311000857
- Call signWhat is a call sign?
- —
- Flag
- Bahamas
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 29,765
- Deadweight (DWT)
- Source: Wikidata, record Q105765973. Added to Voydar on September 23, 2026. Licence: CC0 1.0.52,223 t
- Length overall
- 188 m
- Beam
- 32 m
- Year built
- 2008
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 FORE RIVER, ME (INCLUDED IN STATISTICS FOR PORTLAND HARBOR, ME)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at FORE RIVER, ME (INCLUDED IN STATISTICS FOR PORTLAND HARBOR, ME)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from BostonAuthority-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 Sep 13, 2014衝突 · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)青森県八戸市八戸港北東方沖 八戸市所在の鮫角灯台から真方位033°12.5海里(M)付近
貨物船GLOBAL VANGUARD漁船第三八代丸衝突Report published Feb 26, 2015
A船は、船長A及び航海士Aほか19人が乗り組み、ニッケル鉱約47,000tを積載し、八戸港への入港待ちのために同港北東方沖で船首を南南西方に向けて漂泊中、単独で船橋当直を行っていた航海士Aが、左舷後方にB船を認め、汽笛を鳴らしたが、平成26年9月13日15時01分ごろA船の左舷船首部とB船の右舷船首部とが衝突した。 B船は、船長B及び甲板員Bが乗り組み、青森県三沢市三沢漁港の東方24M付近の漁場でいか釣り漁の操業を終え、同漁港へ向けて八戸港北東方沖を約11ノットの対地速力で自動操舵により西南西進中、船長Bが、操舵室で腰を掛けて見張りを行っていたところ、うとうとした状態となり、衝突直前にA船に気付き、クラッチを切ったが、B船とA船が衝突した。 A船及びB船は、それぞれ自力航行して八戸港及び三沢漁港に着岸した。
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 |
|---|---|---|---|---|
| 2020 | 2,134 t | 677 t | 37 days | 235 kg |
| 2022 | 4,775 t | 1,524 t | 72 days | 285 kg |
| 2023 | 5,294 t | 1,692 t | 74 days | 289 kg |
| 2024 | 4,789 t | 1,527 t | 76 days | 261 kg |
| 2025 | 1,413 t | 452 t | 22 days | 248 kg |
Technical efficiency: EEXI (4.9 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 |
|---|---|---|---|---|
| FORE RIVER, ME (INCLUDED IN STATISTICS FOR PORTLAND HARBOR, ME) | Departure | Jan 17, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| FORE RIVER, ME (INCLUDED IN STATISTICS FOR PORTLAND HARBOR, ME) | Arrival | Jan 17, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Boston USBOS | Departure | Jan 16, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Boston USBOS | Arrival | Jan 16, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Departure | Dec 4, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Arrival | Dec 3, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Dec 1, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Nov 30, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Departure | Nov 26, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Arrival | Nov 26, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Departure | Nov 22, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Nov 22, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: July 7, 2008.
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 River Pearl now?
- Voydar has no displayable AIS position for River Pearl in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is River Pearl?
- River Pearl is a general cargo ship sailing under the flag of Bahamas, built in 2008 by Oshima Shipbuilding. The vessel is 188 m long with a beam of 32 m and has a gross tonnage of 29,765.
- Who is recorded as the owner or manager of River Pearl?
- SMT Shipping (Cyprus) Ltd is recorded as ISM manager for River Pearl (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 River Pearl?
- Voydar has no matched sanctions record displayed for River Pearl 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 River Pearl. Missing records do not establish whether the ship has been detained.
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/9363663Using 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.