ZIM RUBY
Container ship · Singapore · AIS Class A
In short
ZIM RUBY (Container ship, Singapore flag) was last seen on AIS on , moored, near Valencia (Mediterranean Sea). Its crew-entered AIS destination is BARCELONA, with an ETA of Oct 3, 2026, 07:00 UTC; its reported draught is 15.2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 16:54 UTC). Its last detected port call was at Ashdod Southport: arrived Jun 9, 2026, left Jun 13, 2026. ISM manager: Seaspan Ship Management Ltd. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Container ship
- Flag
- Singapore
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- ISM manager
- Seaspan Ship Management Ltd.
Watch this ship
Get an email when ZIM RUBY 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 ZIM RUBY.
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
- 39.4316° N, 0.3183° W
- Area
- Mediterranean Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 351°
- Heading
- 113°
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-upIdentity & particulars
- Name
- ZIM RUBY
- IMO numberWhat is an IMO number?
- 9968009
- MMSIWhat is an MMSI?
- 563293500
- Call signWhat is a call sign?
- 9V7761
- Flag
- Singapore
- AIS ship type
- Cargo (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- Year built
- —
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.
| Date | Event | Source |
|---|---|---|
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Left Ashdod SouthportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Ashdod SouthportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Ashdod SouthportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Ashdod SouthportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Ashdod SouthportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Ashdod SouthportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
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 |
|---|---|---|---|---|
| 2024 | 5,726 t | 2,048 t | 34 days | 423 kg |
| 2025 | 14,575 t | 5,101 t | 67 days | 529 kg |
Technical efficiency: EEXI (7.38 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.
Detected from AIS AIS-detected
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Ashdod Southport ILAST | Jun 9, 2026, 18:12 UTC | Jun 13, 2026, 11:18 UTC | 3 d 17 h |
| Ashdod Southport ILAST | Jun 9, 2026, 17:25 UTC | Jun 9, 2026, 18:09 UTC | 43 min |
| Ashdod Southport ILAST | Jun 9, 2026, 09:48 UTC | Jun 9, 2026, 11:00 UTC | 1 h 12 min |
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 |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | Aug 27, 2026, 03:36 UTC | SOUTH CHEUNG CHAU ANCHORAGE | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Aug 25, 2026, 18:04 UTC | EASTERN UNDEFINED ANCHORAGES | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Apr 28, 2026, 02:37 UTC | SCCA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Dec 29, 2025, 05:41 UTC | SCCA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Sep 15, 2025, 01:08 UTC | SCCA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | May 24, 2025, 06:31 UTC | SCCA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Feb 2, 2025, 21:38 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
Records published by the authority named on each row. Earliest record for this ship: February 2, 2025.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
Frequently asked questions
- Where is ZIM RUBY now?
- ZIM RUBY (Container ship, Singapore flag) was last seen on AIS on Oct 2, 2026, 17:09 UTC, moored, near Valencia (Mediterranean Sea). The crew-entered destination was BARCELONA (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 16:54 UTC). This report does not confirm the ship’s current route.
- What kind of ship is ZIM RUBY?
- ZIM RUBY is a container ship sailing under the flag of Singapore.
- Who is recorded as the owner or manager of ZIM RUBY?
- Seaspan Ship Management Ltd. is recorded as ISM manager for ZIM RUBY (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 ZIM RUBY?
- Voydar has no matched sanctions record displayed for ZIM RUBY 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 ZIM RUBY. 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/9968009Using 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.