Skip to content

Ryoga

General cargo ship · built 2011

IMO9487598No AIS position on record

In short

Ryoga (General cargo ship) has no AIS position on record with Voydar. ISM manager: Stallion Marine Services Ltd (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Flag
—
Year built
2011
Gross tonnage
15,302
Size (length × beam)
158 m × 24 m

Watch this ship

Get an email when Ryoga 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 Ryoga.

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-up

Identity & particulars

Name
Ryoga
IMO numberWhat is an IMO number?
9487598
Flag
—
Gross tonnageGross tonnage vs deadweight
15,302
Length overall
158.1 m
Beam
24 m
Year built
2011

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

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.

DateEventSource
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from PortlandAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at VancouverAuthority-reportedUSACE 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.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20211,957 t628 t41 days185 kg
20221,937 t620 t38 days219 kg
20231,689 t535 t31 days210 kg
20243,258 t1,038 t85 days238 kg
20252,173 t689 t51 days202 kg

Technical efficiency: EEXI (7.4 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

PortRecordDate (UTC)BerthSource
Hong Kong HKHKGArrivalMar 18, 2019, 10:27 UTCCCMHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Portland USPDXDepartureSep 26, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Vancouver USVANArrivalSep 14, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Portland USPDXDepartureApr 24, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Vancouver USVANArrivalApr 21, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Sacramento USSACDepartureDec 6, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Sacramento USSACArrivalDec 1, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Sacramento USSACDepartureJul 29, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Sacramento USSACArrivalJul 26, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Sacramento USSACDepartureJun 14, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Sacramento USSACArrivalJun 9, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Sacramento USSACDepartureMay 3, 2012(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: April 28, 2012.

Frequently asked questions

Where is Ryoga now?
Voydar has no displayable AIS position for Ryoga in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Ryoga?
Ryoga is a general cargo ship, built in 2011. The vessel is 158.1 m long with a beam of 24 m and has a gross tonnage of 15,302.
Who is recorded as the owner or manager of Ryoga?
Stallion Marine Services Ltd is recorded as ISM manager for Ryoga (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 Ryoga?
Voydar has no matched sanctions record displayed for Ryoga from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Ryoga. 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/9487598
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

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.

See plans