Onego Rio
General cargo ship · Netherlands · built 2003 · AIS Class A
In short
Onego Rio (General cargo ship, Netherlands flag) was last seen on AIS on , moored, near Rotterdam (North Sea). Its crew-entered AIS destination is MIDDLESBROUGH, with an ETA of Oct 5, 2026, 13:00 UTC; its reported draught is 4.7 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 10:12 UTC). Registered owner: Onego Rio B.V. (source: ILT — Nederlands vlagregister (Netherlands flag register data)).
Current voyage: from Waterford Great Island (ESB) (departed Sep 24, 2026, 16:13 UTC) to MIDDLESBROUGH
- Vessel type
- General cargo ship
- Flag
- Netherlands
- Year built
- 2003
- Gross tonnage
- 7,576
- Size (length × beam)
- 143 m × 18 m
- Registered owner
- Onego Rio B.V.
Watch this ship
Get an email when Onego Rio 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 Onego Rio.
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
- 51.8908° N, 4.457° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 99°
- Heading
- 286°
Last 30 days: 2 port calls (Waterford Great Island (ESB) and Saint-Lambert).
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
- Onego Rio
- IMO numberWhat is an IMO number?
- 9258985
- MMSIWhat is an MMSI?
- 244150212
- Call signWhat is a call sign?
- PBYD
- Flag
- Netherlands
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 7,576
- Deadweight (DWT)
- Source: Wikidata, record Q84260631. Added to Voydar on September 23, 2026. Licence: CC0 1.0.10,300 t
- Length overall
- 142.8 m
- Beam
- 18.3 m
- Year built
- 2003
NetherlandsA 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.
- Registered owner
- Onego Rio B.V.(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · confidence 0.9 · retrieved Oct 1, 2026
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Sep 28, 2026Source: EU MRV (THETIS-MRV) emissions · reporting year 2024 · reported · confidence 0.9 · retrieved Sep 28, 2026
- Builder
- DAMEN SHIPYARD OKEAN(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · confidence 0.9 · retrieved Oct 1, 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 |
|---|---|---|
| Left Waterford Great Island (ESB)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Waterford Great Island (ESB)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Saint-LambertAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Saint-LambertAIS-detected | Voydar port-call detector (AIS geofence) | |
| ISM manager: Onego Rio CV (previously TAS Transatlantische Schifffahrts GmbH & Co. KG) | Voydar relationship-change derivation (derived by Voydar from EU MRV (THETIS-MRV) emissions) | |
| Reported departure from GalvestonAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at GalvestonAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at Panama CityAuthority-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 | 6,863 t | 2,185 t | 174 days | 154 kg |
| 2019 | 5,449 t | 1,730 t | 162 days | 149 kg |
| 2020 | 6,475 t | 2,057 t | 144 days | 160 kg |
| 2021 | 8,189 t | 2,586 t | 165 days | 175 kg |
| 2022 | 9,051 t | 2,854 t | 181 days | 167 kg |
| 2023 | 5,614 t | 1,789 t | 172 days | 164 kg |
| 2024 | 5,015 t | 1,588 t | 126 days | 148 kg |
| 2025 | 6,514 t | 2,070 t | 162 days | 151 kg |
Technical efficiency: EIV (28.17 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 |
|---|---|---|---|
| Waterford Great Island (ESB) IEWGI | Sep 22, 2026, 15:44 UTC | Sep 24, 2026, 16:13 UTC | 2 d 0 h |
| Saint-Lambert CASLT | Sep 12, 2026, 15:08 UTC | Sep 12, 2026, 15:59 UTC | 52 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 |
|---|---|---|---|---|
| Galveston USGLS | Departure | Dec 16, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Galveston USGLS | Arrival | Dec 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Panama City USPFN | Arrival | Dec 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Panama City USPFN | Departure | Dec 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Departure | Oct 25, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Arrival | Oct 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Jun 2, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Jun 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Departure | May 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Arrival | May 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Everglades USPEF | Departure | Jun 2, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Everglades USPEF | Arrival | Jun 2, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: April 7, 2003.
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 |
|---|---|---|
| Sep 24, 2026, 16:40 UTC | Draught change Reported draught went from 7.4 m to 4.7 m after leaving Waterford Great Island (ESB). 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
- Where is Onego Rio now?
- Onego Rio (General cargo ship, Netherlands flag) was last seen on AIS on Oct 4, 2026, 10:46 UTC, moored, near Rotterdam (North Sea). The crew-entered destination was MIDDLESBROUGH (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 10:12 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Onego Rio?
- Onego Rio is a general cargo ship sailing under the flag of Netherlands, built in 2003. The vessel is 142.8 m long with a beam of 18.3 m and has a gross tonnage of 7,576.
- Who is recorded as the owner or manager of Onego Rio?
- Onego Rio B.V. is recorded as Registered owner for Onego Rio (source: ILT — Nederlands vlagregister (Netherlands flag register data)). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for Onego Rio?
- Voydar has no matched sanctions record displayed for Onego Rio 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 Onego Rio. Missing records do not establish whether the ship has been detained.
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/9258985Using 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.