Rixta Oldendorff
Bulk carrier · Liberia · built 2011 · AIS Class A
In short
Rixta Oldendorff (Bulk carrier, Liberia flag) was last seen on AIS on , under way at 9.4 kn, in the Caribbean Sea. 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 PANAMA CANAL; its reported draught is 14.3 m (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 03:02 UTC). ISM manager: Oldendorff Carriers GmbH & Co. KG (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
- Vessel type
- Bulk carrier
- Flag
- Liberia
- Year built
- 2011
- Gross tonnage
- 65,950
- Size (length × beam)
- 260 m × 43 m
- ISM manager
- Oldendorff Carriers GmbH & Co. KG
Watch this ship
Get an email when Rixta Oldendorff 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 Rixta Oldendorff.
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
- 11.3448° N, 74.4425° W
- Area
- Caribbean Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 9.4 kn
- Course
- 295°
- Heading
- 294°
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
- Rixta Oldendorff
- IMO numberWhat is an IMO number?
- 9598567
- MMSIWhat is an MMSI?
- 636092978
- Call signWhat is a call sign?
- D5YK5
- Flag
- Liberia
- Vessel type
- Bulk carrier
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 65,950
- Deadweight (DWT)
- Source: Wikidata, record Q83632534. Added to Voydar on September 23, 2026. Licence: CC0 1.0.118,863 t
- Length overall
- 260 m
- Beam
- 43 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.
| 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 BaltimoreAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at BaltimoreAuthority-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 |
|---|---|---|---|---|
| 2018 | 10,051 t | 3,210 t | 106 days | 449 kg |
| 2019 | 5,006 t | 1,598 t | 108 days | 308 kg |
| 2020 | 1,958 t | 628 t | 16 days | 551 kg |
| 2022 | 15,314 t | 4,905 t | 125 days | 484 kg |
| 2023 | 10,628 t | 3,407 t | 113 days | 448 kg |
| 2025 | 14,429 t | 4,624 t | 138 days | 402 kg |
Technical efficiency: EEXI (2.89 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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | Nov 7, 2024, 15:32 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Baltimore USBAL | Departure | Aug 28, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Arrival | Aug 27, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Jul 19, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Arrival | Jul 17, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Departure | Mar 18, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Arrival | Mar 10, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Departure | Oct 7, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CHESAPEAKE BAY, MD AND VA | Arrival | Oct 5, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Departure | Apr 11, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CHESAPEAKE BAY, MD AND VA | Arrival | Mar 26, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Departure | May 27, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: November 11, 2012.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is Rixta Oldendorff now?
- Rixta Oldendorff (Bulk carrier, Liberia flag) was last seen on AIS on Sep 26, 2026, 03:23 UTC, under way at 9.4 kn, in the Caribbean Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was PANAMA CANAL (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 03:02 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Rixta Oldendorff?
- Rixta Oldendorff is a bulk carrier sailing under the flag of Liberia, built in 2011. The vessel is 260 m long with a beam of 43 m and has a gross tonnage of 65,950.
- Who is recorded as the owner or manager of Rixta Oldendorff?
- Oldendorff Carriers GmbH & Co. KG is recorded as ISM manager for Rixta Oldendorff (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 Rixta Oldendorff?
- Voydar has no matched sanctions record displayed for Rixta Oldendorff 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 Rixta Oldendorff. 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/9598567Using 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.