Skip to content

Red Diamond

Bulk carrier · Liberia · built 2011 · AIS Class A

IMO9331713MMSI636014524Call signA8UM9Last AIS position Sep 30, 2026, 10:59 UTC

In short

Red Diamond (Bulk carrier, Liberia flag) was last seen on AIS on , under way at 12.1 kn, near Namikata (North Pacific Ocean). 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 PHFER; its reported draught is 10.8 m (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 10:26 UTC). ISM manager: ASM Maritime BV (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Vessel type
Bulk carrier
Year built
2011
Gross tonnage
32,637
Size (length × beam)
190 m × 32 m
ISM manager
ASM Maritime BV

Watch this ship

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

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
34.113° N, 132.8282° E
Area
North Pacific Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
12.1 kn
Course
217°
Heading
215°
34.113° N, 132.8282° E
Open the full live map →

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

Identity & particulars

Name
Red Diamond
IMO numberWhat is an IMO number?
9331713
MMSIWhat is an MMSI?
636014524
Call signWhat is a call sign?
A8UM9
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
32,637
Length overall
190 m
Beam
32.3 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 year 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 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 PORT OF PLAQUEMINES, LAAuthority-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
20188,877 t2,845 t92 days367 kg
20213,444 t1,103 t37 days303 kg
20226,583 t2,104 t108 days326 kg
20235,398 t1,721 t94 days265 kg
20254,251 t1,357 t61 days272 kg

Technical efficiency: EIV (5.98 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 HKHKGArrival(matched by call sign)Dec 8, 2024, 12:58 UTCPTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalOct 16, 2024, 17:43 UTCSELAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
PORT OF PLAQUEMINES, LADepartureJul 21, 2015(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LAArrivalJul 12, 2015(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureDec 15, 2014(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalNov 30, 2014(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYDepartureNov 24, 2014(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalNov 23, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Tampa USTPADepartureNov 21, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Tampa USTPAArrivalNov 21, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVDepartureNov 17, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVArrivalNov 17, 2014(date only)—USACE foreign traffic vessel entrances & clearances

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

Behaviour at sea Voydar-derived

Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.

WhenWhat we observedConfidence
Sep 16, 2026, 09:31 UTC
AIS gap

No AIS position received for 7 d 13 h while our receivers kept hearing other ships there (72 of 72 hours in coverage). Heard again 11 km away.

Method seadar.behaviour.ais_gap v1

High (90%)

Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.

Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.

How these are computed →

Frequently asked questions

Where is Red Diamond now?
Red Diamond (Bulk carrier, Liberia flag) was last seen on AIS on Sep 30, 2026, 10:59 UTC, under way at 12.1 kn, near Namikata (North Pacific Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was PHFER (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 10:26 UTC). This report does not confirm the ship’s current route.
What kind of ship is Red Diamond?
Red Diamond is a bulk carrier sailing under the flag of Liberia, built in 2011. The vessel is 190 m long with a beam of 32.3 m and has a gross tonnage of 32,637.
Who is recorded as the owner or manager of Red Diamond?
ASM Maritime BV is recorded as ISM manager for Red Diamond (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 Red Diamond?
Voydar has no matched sanctions record displayed for Red Diamond 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 Red Diamond. 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/9331713
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