Skip to content

RIDER

Container ship · Antigua & Barbuda · built 2006 · AIS Class A

IMO9322566MMSI304922000Call signV2BT5Last AIS position Oct 3, 2026, 09:34 UTC

In short

RIDER (Container ship, Antigua & Barbuda flag) was last seen on AIS on , under way at 16 kn, in the Bay of Biscay. Its crew-entered AIS destination is GBLON (London), with an ETA of Oct 5, 2026, 03:15 UTC; its reported draught is 7.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 23:25 UTC). ISM manager: Schiffahrts UG (haftungsbeschrankt) & Co. KG MS "Rider" (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Current voyage: from Rotterdam (departed Sep 30, 2026, 04:29 UTC) to GBLON (London)

Vessel type
Container ship
Year built
2006
Gross tonnage
7,852
Size (length × beam)
141 m

Watch this ship

Get an email when RIDER 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 RIDER.

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.

Photo of RIDER
Photo: kees torn · Licence: CC BY-SA 2.0 · via Wikimedia Commons

Last reported position

received
Position
45.994° N, 4.6917° W
Area
Bay of Biscay
StatusWhat do AIS statuses mean?
Under way using engine
Speed
16 kn
Course
346°
Heading
345°
45.994° N, 4.6917° W
Open the full live map →

Last 30 days: 4 port calls (Rotterdam, Tilbury, and Santander).

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-up

Identity & particulars

Name
RIDER
IMO numberWhat is an IMO number?
9322566
MMSIWhat is an MMSI?
304922000
Call signWhat is a call sign?
V2BT5
AIS ship type
Cargo (hazardous cat. A)
Gross tonnageGross tonnage vs deadweight
7,852
Length overall
140.6 m
Beam
—
Year built
2006

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
Source: EU MRV (THETIS-MRV) emissions · reporting year 2024 · reported · confidence 0.9 · retrieved Sep 28, 2026
Builder
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 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.

DateEventSource
Left RotterdamAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at RotterdamAIS-detectedVoydar port-call detector (AIS geofence)
Left TilburyAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at TilburyAIS-detectedVoydar port-call detector (AIS geofence)
Left SantanderAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at SantanderAIS-detectedVoydar port-call detector (AIS geofence)
ISM manager: Schiffahrts UG (haftungsbeschrankt) & Co. KG MS "Rider" (previously MS "JSP Rider" Schifffahrts UG (haft.) & Co. KG)Voydar relationship-change derivation (derived by Voydar from EU MRV (THETIS-MRV) emissions)

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.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
201812,370 t3,914 t216 days225 kg
201917,028 t5,368 t199 days238 kg
202016,763 t5,254 t183 days265 kg
202115,015 t4,716 t183 days231 kg
20226,376 t2,012 t77 days244 kg
20234,985 t1,585 t66 days247 kg
202413,752 t4,354 t222 days211 kg
202518,792 t5,917 t254 days227 kg

Technical efficiency: EIV (38.93 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

PortArrivedDepartedTime in port
Rotterdam NLRTMSep 29, 2026, 10:42 UTCSep 30, 2026, 04:29 UTC17 h 47 min
Tilbury GBTILSep 28, 2026, 00:32 UTCSep 28, 2026, 23:06 UTC22 h 34 min
Santander ESSDRSep 25, 2026, 04:29 UTCSep 25, 2026, 17:53 UTC13 h 24 min
Rotterdam NLRTMSep 22, 2026, 12:52 UTCSep 23, 2026, 03:42 UTC14 h 50 min
Poortugaal NLPTGAug 26, 2026, 04:15 UTCSep 9, 2026, 01:26 UTC13 d 21 h

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.

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.

WhenWhat we observedConfidence
Sep 30, 2026, 03:30 UTC
Draught change

Reported draught went from 6.3 m to 7.2 m while in port at Rotterdam. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 28, 2026, 22:37 UTC
Draught change

Reported draught went from 7.4 m to 6.3 m while in port at Tilbury. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 23, 2026, 03:03 UTC
Draught change

Reported draught went from 6.3 m to 7 m while in port at Rotterdam. Voydar infers the ship probably loaded 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.

How these are computed →

Frequently asked questions

Where is RIDER now?
RIDER (Container ship, Antigua & Barbuda flag) was last seen on AIS on Oct 3, 2026, 09:34 UTC, under way at 16 kn, in the Bay of Biscay. The crew-entered destination was GBLON (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 23:25 UTC). This report does not confirm the ship’s current route.
What kind of ship is RIDER?
RIDER is a container ship sailing under the flag of Antigua & Barbuda, built in 2006 by Damen Shipyards Galați. The vessel is 140.6 m long and has a gross tonnage of 7,852.
Who is recorded as the owner or manager of RIDER?
Schiffahrts UG (haftungsbeschrankt) & Co. KG MS "Rider" is recorded as ISM manager for RIDER (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 RIDER?
Voydar has no matched sanctions record displayed for RIDER 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 RIDER. 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/9322566
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using 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.

See plans