Rubymar
Bulk carrier · built 1997
In short
Rubymar (Bulk carrier) is a historical vessel, built in 1997; its service ended in 2024. It predates AIS tracking, so Voydar has no position for it.
Known for: Sank, Red Sea, Mar 1, 2024 · Source: Wikidata
- Vessel type
- Bulk carrier
- Flag
- —
- Year built
- 1997
- Gross tonnage
- —
- Size (length × beam)
- 172 m × 27 m
- Registered owner
- —

Position: none on record
Rubymar predates AIS, the radio system Voydar tracks ships with, so there is no position or track to show. Its identity, particulars and history are below.
Identity & particulars
Length overall 171.6 mone tick every 25 m
Beam 27 mPlan outline, to scale
- Name
- Rubymar
- IMO numberWhat is an IMO number?
- 9138898
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- Bulk carrier
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- 171.6 m
- Beam
- 27 m
- Year built
- 1997
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.
- 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 |
|---|---|---|
| Reported departure from Corpus ChristiAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at Corpus ChristiAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from ELIZABETH RIVER (SOUTHERN BRANCH) VAAuthority-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 | 3,121 t | 997 t | 42 days | 255 kg |
| 2019 | 4,393 t | 1,399 t | 72 days | 243 kg |
Technical efficiency: EIV (6.88 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 2019 sits among the ships EU MRV lists as “Bulk carrier”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile16 g per tonne-nautical mile
- Lowest reportedHighest reported
90% of the 3,402 ships in this group reported a lower figure.
Group: lower quartile 6.41 · median 8.42 · upper quartile 11.29
- CO₂ per nautical mile sailed243.1 kg per nautical mile
- Lowest reportedHighest reported
26% of the 3,460 ships in this group reported a lower figure.
Group: lower quartile 241.9 · median 286.3 · upper quartile 337.3
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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Corpus Christi USCRP | Departure | Jun 21, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Arrival | Jun 18, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Departure | May 6, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Arrival | May 5, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PENN MANOR AREA, PA | Departure | May 2, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PENN MANOR AREA, PA | Arrival | Apr 30, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Departure | Apr 26, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Arrival | Apr 25, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Departure | Jun 26, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Arrival | Jun 16, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Tacoma USTIW | Departure | Mar 25, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Tacoma USTIW | Arrival | Mar 21, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: February 1, 2002.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
About Rubymar
MV Rubymar was a Belize-flagged Handymax-size bulk carrier cargo ship completed in 1997. She previously sailed under the names Ken Shin from 1997, Chatham Island from 2009, and Ikaria Island from 2020, before being renamed Rubymar. On 18 February 2024, the ship was struck by a Houthi anti-ship missile during the Red Sea crisis while carrying a cargo of fertilizer. After being adrift for weeks, the ship sank on 2 March as a result of the strike, becoming the first vessel lost due to a Houthi attack during the crisis. The wreck poses a risk to navigation of the Red Sea, and also has the potential to cause environmental damage due to the leakage of its oil and fertilizer.
Summary from Wikipedia, licensed CC BY-SA.
Frequently asked questions
- What kind of ship is Rubymar?
- Rubymar is a bulk carrier, built in 1997 by Onomichi Dockyard. The vessel is 171.6 m long with a beam of 27 m.
- What sanctions and inspection records does Voydar hold for Rubymar?
- Voydar has no matched sanctions record displayed for Rubymar 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 Rubymar. 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
More Bulk carriers
Other bulk carriers with full Voydar profiles. A different set each day. All bulk carriers
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/9138898Cite this page
Rubymar. Voydar (voydar.com). https://www.voydar.com/vessel/9138898-rubymar. 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.