Rix Crystal
General cargo ship · Cyprus · built 1993 · AIS Class A
In short
Rix Crystal (General cargo ship, Cyprus flag) was last seen on AIS on , under way at 6.2 kn, in the North Sea. Its crew-entered AIS destination is DE REN (Rendsburg), with an ETA of Nov 19, 2026, 12:00 UTC; its reported draught is 5.8 m (voyage report via AISstream.io global terrestrial AIS, received Nov 17, 2026, 17:40 UTC). ISM manager: Rix Shipmanagement (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
Current voyage: from Rekefjord (departed Nov 17, 2026, 07:15 UTC) to DE REN (Rendsburg)
- Vessel type
- General cargo ship
- Flag
- Cyprus
- Year built
- 1993
- Gross tonnage
- —
- Size (length × beam)
- 85 m × 13 m
- ISM manager
- Rix Shipmanagement

Last reported position: 57.9011° N, 8.3267° E · North Sea · See on the map
Watch this ship
Get an email when Rix Crystal reaches Rendsburg, and when it leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
What you would have been told
Following Rix Crystal over the last 24 hours would have sent 1 message.
- LeftRekefjord
Detected from AIS, as of Nov 17, 2026, 17:41 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Rix Crystal 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: Voydar for iPhone
Last reported position
received- Position
- 57.9011° N, 8.3267° E
- Area
- North Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 6.2 kn
- Course
- 95°
- Heading
- 95°
- Compass: course over ground 95°, heading 95°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: at least 12 port calls (Rekefjord, Haseldorf, Hamburg, Brunsbuttel, Holtenau, Warnemunde, Hundested, Fredrikstad, Skjarhalden, Heroya, and Randaberg).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Data delivered by BarentsWatch
A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 85.2 mone tick every 10 m
Beam 13.1 mPlan outline, to scale
- Name
- Rix Crystal
- IMO numberWhat is an IMO number?
- 9050125
- MMSIWhat is an MMSI?
- 212821000
- Call signWhat is a call sign?
- P3CZ5
- Flag
- Cyprus
- Vessel type
- General cargo ship
- Gross tonnageGross tonnage vs deadweight
- —
- Deadweight (DWT)
- Source: Wikidata, record Q83627611. Added to Voydar on October 23, 2026. Licence: CC0 1.0.3,834 t
- Length overall
- 85.2 m
- Beam
- 13.1 m
- Year built
- 1993
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 · high confidence · retrieved Nov 16, 2026
- 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 |
|---|---|---|
| Left RekefjordAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at RekefjordAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HaseldorfAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HaseldorfAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HamburgAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HamburgAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at GdanskAuthority-reported | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) | |
| Reported departure from WilmingtonAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at WilmingtonAuthority-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 |
|---|---|---|---|---|
| 2025 | 1,802 t | 562 t | 121 days | 79 kg |
Technical efficiency: EEXI (14.84 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 “General cargo ship”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile43.39 g per tonne-nautical mile
- Lowest reportedHighest reported
76% of the 661 ships in this group reported a lower figure.
Group: lower quartile 23.23 · median 30.36 · upper quartile 42.59
- CO₂ per nautical mile sailed79.5 kg per nautical mile
- Lowest reportedHighest reported
30% of the 2,956 ships in this group reported a lower figure.
Group: lower quartile 74.8 · median 110.6 · upper quartile 185.8
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 |
|---|---|---|---|
| Rekefjord NOREK | Nov 16, 2026, 09:10 UTC | Nov 17, 2026, 07:15 UTC | 22 h 5 min |
| Haseldorf DEHLO | Nov 14, 2026, 04:08 UTC | Nov 14, 2026, 06:43 UTC | 2 h 35 min |
| Hamburg DEHAM | Nov 12, 2026, 06:58 UTC | Nov 12, 2026, 13:02 UTC | 6 h 3 min |
| Haseldorf DEHLO | Nov 11, 2026, 12:10 UTC | Nov 12, 2026, 05:13 UTC | 17 h 3 min |
| Brunsbuttel DEBRB | Nov 11, 2026, 09:01 UTC | Nov 11, 2026, 10:39 UTC | 1 h 38 min |
| Holtenau DEHTU | Nov 11, 2026, 00:23 UTC | Nov 11, 2026, 01:38 UTC | 1 h 14 min |
| Warnemunde DEWAR | Nov 5, 2026, 09:42 UTC | Nov 10, 2026, 15:51 UTC | 5 d 6 h |
| Hundested DKHUN | Nov 2, 2026, 03:56 UTC | Nov 2, 2026, 08:29 UTC | 4 h 33 min |
| Fredrikstad NOFRK | Oct 29, 2026, 22:31 UTC | Oct 30, 2026, 21:26 UTC | 22 h 55 min |
| Skjarhalden NOSKH | Oct 28, 2026, 22:54 UTC | Oct 29, 2026, 21:38 UTC | 22 h 44 min |
| Heroya NOHRY | Oct 27, 2026, 22:21 UTC | Oct 28, 2026, 17:31 UTC | 19 h 10 min |
| Randaberg NORDB | Oct 25, 2026, 23:11 UTC | Oct 26, 2026, 16:23 UTC | 17 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 |
|---|---|---|---|---|
| Gdansk PLGDN | Arrival | Oct 16, 2026, 17:50 UTC | Elewator 3/4 | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) |
| Wilmington USILM | Departure | Apr 16, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Wilmington USILM | Arrival | Apr 16, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
| LITTLE RIVER (CREEK), VA | Departure | Jan 23, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
| LITTLE RIVER (CREEK), VA | Arrival | Jan 22, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
| LITTLE RIVER (CREEK), VA | Departure | Dec 25, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| LITTLE RIVER (CREEK), VA | Arrival | Dec 25, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| LITTLE RIVER (CREEK), VA | Departure | Nov 28, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| LITTLE RIVER (CREEK), VA | Arrival | Nov 28, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| LITTLE RIVER (CREEK), VA | Departure | Nov 2, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| LITTLE RIVER (CREEK), VA | Arrival | Nov 2, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| LITTLE RIVER (CREEK), VA | Departure | Oct 9, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: April 1, 2002.
Source: Urząd Morski w Gdyni (www.umgdy.gov.pl); processed by Seadar (times converted to UTC, IMO checksum-validated). The retrieval date is shown with the data. Licence: Polish PSI reuse (ustawa o otwartych danych), conditions: cite source, date, processing.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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 |
|---|---|---|
| Nov 12, 2026, 11:28 UTC | Draught change Reported draught went from 5.6 m to 3.6 m while in port at Hamburg. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 8, 2026, 20:55 UTC | Draught change Reported draught went from 5.8 m to 3.6 m while in port at Warnemunde. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 30, 2026, 18:53 UTC | Draught change Reported draught went from 3.5 m to 6.3 m while in port at Fredrikstad. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 28, 2026, 14:04 UTC | Draught change Reported draught went from 4.8 m to 3.5 m while in port at Heroya. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 26, 2026, 14:09 UTC | Draught change Reported draught went from 3.6 m to 4.8 m while in port at Randaberg. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 26, 2026, 05:12 UTC | Draught change Reported draught went from 5.8 m to 3.6 m while in port at Randaberg. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 22, 2026, 16:40 UTC | Draught change Reported draught went from 3.6 m to 5.8 m while in port at Stavanger. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 17, 2026, 12:16 UTC | Draught change Reported draught went from 3.5 m to 6 m while in port at Nowe Warpno. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.
Source: BarentsWatch AIS API. Data delivered by BarentsWatch (NLOD 2.0; data owner: Kystverket). Licence: NLOD 2.0 (BarentsWatch API terms 2023-11-02; Live/Historic AIS OpenAPI licence NLOD).
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 Rix Crystal?
- Rix Crystal is a general cargo ship sailing under the flag of Cyprus, built in 1993 by Elbewerft Boizenburg. The vessel is 85.2 m long with a beam of 13.1 m.
- Who is recorded as the owner or manager of Rix Crystal?
- Rix Shipmanagement is recorded as ISM manager for Rix Crystal (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 Rix Crystal?
- Voydar has no matched sanctions record displayed for Rix Crystal 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 Rix Crystal. 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
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/9050125Cite this page
Rix Crystal. Voydar (voydar.com). https://www.voydar.com/vessel/9050125-rix-crystal. Retrieved November 17, 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.