ZIM RUBY
Container ship · Singapore · AIS Class A
In short
ZIM RUBY (Container ship, Singapore flag) was last seen on AIS on , under way at 17.7 kn, near Sungai Udang Port (Strait of Malacca). Its last detected port call was at Ashdod: arrived Oct 15, 2026, left Oct 16, 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, AIS-reported (length × beam)
- 272 m × 43 m
- ISM manager
- Seaspan Ship Management Ltd.
Last reported position: 2.1204° N, 101.9665° E · Strait of Malacca · See on the map
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.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 20, 2026, 19:46 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for ZIM RUBY reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans
Get alerts on your phone: the Voydar app
Last reported position
received- Position
- 2.1204° N, 101.9665° E
- Area
- Strait of Malacca
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 17.7 kn
- Course
- 131°
- Heading
- 130°
- Compass: course over ground 131°, heading 130°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
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.
Pro shows ZIM RUBY's track before the last 30 days. Voydar has recorded its port calls since June 9, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
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 (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 7, 2026.272 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 7, 2026.43 m
- 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.
AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via AISstream.io global terrestrial AIS on November 7, 2026.
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 · high confidence · retrieved Nov 16, 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 |
|---|---|---|
| Left AshdodAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at AshdodAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HaifaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HaifaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HaifaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HaifaAIS-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) | |
| 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) |
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.
Compared with ships of its type
Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “Container ship”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile8.05 g per tonne-nautical mile
- Lowest reportedHighest reported
15% of the 2,233 ships in this group reported a lower figure.
Group: lower quartile 9.85 · median 16.45 · upper quartile 29.35
- CO₂ per nautical mile sailed528.5 kg per nautical mile
- Lowest reportedHighest reported
49% of the 2,256 ships in this group reported a lower figure.
Group: lower quartile 313.5 · median 541.9 · upper quartile 768.9
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.
Detected from AIS AIS-detected
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Ashdod ILASH | Oct 15, 2026, 13:37 UTC | Oct 16, 2026, 14:28 UTC | 24 h 51 min |
| Haifa ILHFA | Oct 11, 2026, 11:49 UTC | Oct 12, 2026, 04:02 UTC | 16 h 14 min |
| Haifa ILHFA | Oct 11, 2026, 06:38 UTC | Oct 11, 2026, 11:11 UTC | 4 h 33 min |
| Haifa ILHFA | Oct 10, 2026, 17:48 UTC | Oct 11, 2026, 06:17 UTC | 12 h 29 min |
| Genova ITGOA | Oct 6, 2026, 03:48 UTC | Oct 7, 2026, 04:19 UTC | 24 h 31 min |
| Barcelona ESBCN | Oct 3, 2026, 17:20 UTC | Oct 5, 2026, 01:47 UTC | 32 h 27 min |
| Valencia ESVLC | Sep 28, 2026, 00:07 UTC | Oct 3, 2026, 05:58 UTC | 5 d 5 h |
| Haifa ILHFA | Jun 14, 2026, 21:43 UTC | Jun 15, 2026, 20:35 UTC | 22 h 52 min |
| 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.
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.
| When | What we observed | Confidence |
|---|---|---|
| Oct 16, 2026, 15:00 UTC | Draught change Reported draught went from 11.8 m to 11 m after leaving Ashdod. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Oct 6, 2026, 18:12 UTC | Draught change Reported draught went from 13.7 m to 12.6 m while in port at Genova. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
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.
Frequently asked questions
- 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, 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 ZIM RUBY. 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 Container ships
Other container ships with full Voydar profiles. A different set each day. All container ships
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/9968009Cite this page
ZIM RUBY. Voydar (voydar.com). https://www.voydar.com/vessel/9968009-zim-ruby. Retrieved November 20, 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.