Skip to content

RIKKE B

General cargo ship · Cyprus · built 2012 · AIS Class A

IMO9574315MMSI210524000Call sign5BCM6Last AIS position Oct 5, 2026, 08:40 UTC

In short

RIKKE B (General cargo ship, Cyprus flag) was last seen on AIS on , under way at 11.5 kn, near Nysted (Baltic Sea). Its crew-entered AIS destination is DERSK (Rostock), with an ETA of Oct 5, 2026, 13:00 UTC; its reported draught is 5.6 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 08:12 UTC). ISM manager: Schifffahrtsgesellschaft Tom B mbH & Co. KG (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Current voyage: from Holtenau (departed Oct 5, 2026, 03:50 UTC) to DERSK (Rostock)

Flag
Cyprus
Year built
2012
Gross tonnage
2,588
Size (length × beam)
88 m × 13 m

Watch this ship

Get an email when RIKKE B reaches Rostock, and when it leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

Free forever. No card. A free account follows up to 5 ships and ports.

Photo of RIKKE B
Photo: Alf van Beem · Licence: CC0 · via Wikimedia Commons

Last reported position

received
Position
54.4586° N, 11.6029° E
Area
Baltic Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
11.5 kn
Course
119°
Heading
123°
54.4586° N, 11.6029° E
Open the full live map →

Last 30 days: 5 port calls (Holtenau, Rotterdam, Sheerness, Kiel, and Kiel Canal).

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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
RIKKE B
IMO numberWhat is an IMO number?
9574315
MMSIWhat is an MMSI?
210524000
Call signWhat is a call sign?
5BCM6
Flag
Cyprus
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
2,588
Length overall
88.3 m
Beam
13 m
Year built
2012

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 Oct 5, 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 HoltenauAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at HoltenauAIS-detectedVoydar port-call detector (AIS geofence)
Left RotterdamAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at RotterdamAIS-detectedVoydar port-call detector (AIS geofence)
Left SheernessAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at SheernessAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from Morehead CityAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Port State Control inspection at ATLANTIC BEACH, North CarolinaUSCG PSIX / CGMIX inspections
Reported arrival at Morehead CityAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Inspection at WASHINGTON, District of ColumbiaUSCG PSIX / CGMIX inspections
Inspection at Wilmington, North CarolinaUSCG PSIX / CGMIX inspections

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.

Safety & inspections

3
Inspections
not recorded
Detentions
0
Deficiencies
DateTypePortFindings
Sep 22, 2013Vessel InspectionPSCATLANTIC BEACH, North Carolinaclean
Sep 19, 2013Incident InvestigationWASHINGTON, District of Columbiaclean
Sep 14, 2013Vessel Transfer MonitorWilmington, North Carolinaclean

Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.

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
20253,694 t1,152 t187 days89 kg

Technical efficiency: EEXI (13.8 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
Holtenau DEHTUOct 5, 2026, 02:41 UTCOct 5, 2026, 03:50 UTC1 h 9 min
Rotterdam NLRTMOct 2, 2026, 01:22 UTCOct 3, 2026, 14:40 UTC37 h 18 min
Sheerness GBSHSSep 27, 2026, 13:24 UTCSep 30, 2026, 17:27 UTC3 d 4 h
Kiel DEKELSep 25, 2026, 10:54 UTCSep 25, 2026, 14:33 UTC3 h 39 min
Kiel Canal DECKLSep 14, 2026, 16:58 UTCSep 14, 2026, 17:56 UTC58 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

PortRecordDate (UTC)BerthSource
Morehead City USMRHDepartureSep 23, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Morehead City USMRHArrivalSep 22, 2013(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: September 22, 2013.

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 29, 2026, 07:07 UTC
Draught change

Reported draught went from 5.7 m to 4 m while in port at Sheerness. 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.

How these are computed →

Frequently asked questions

Where is RIKKE B now?
RIKKE B (General cargo ship, Cyprus flag) was last seen on AIS on Oct 5, 2026, 08:40 UTC, under way at 11.5 kn, near Nysted (Baltic Sea). The crew-entered destination was DERSK (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 08:12 UTC). This report does not confirm the ship’s current route.
What kind of ship is RIKKE B?
RIKKE B is a general cargo ship sailing under the flag of Cyprus, built in 2012. The vessel is 88.3 m long with a beam of 13 m and has a gross tonnage of 2,588.
Who is recorded as the owner or manager of RIKKE B?
Schifffahrtsgesellschaft Tom B mbH & Co. KG is recorded as ISM manager for RIKKE B (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 RIKKE B?
Voydar has no matched sanctions record displayed for RIKKE B 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. RIKKE B has 3 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.

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/9574315
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