Skip to content

Bianca Rambow

Container ship · Germany · built 2004 · AIS Class A

IMO9297591MMSI211141000Call signDIFTLast AIS position Oct 4, 2026, 02:03 UTC

In short

Bianca Rambow (Container ship, Germany flag) was last seen on AIS on , not moving, in the port of Holtenau. Its crew-entered AIS destination is SEHEL (Helsingborg), with an ETA of Oct 4, 2026, 14:15 UTC; its reported draught is 8.6 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 01:12 UTC). It arrived there on Oct 4, 2026, 00:50 UTC. ISM manager: Reederei Rambow GmbH & Co. KG MS “Bianca Rambow” (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Container ship
Year built
2004
Gross tonnage
9,981
Size (length × beam)
134 m × 23 m

Watch this ship

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

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 BIANCA RAMBOW
Photo: Eduard47 · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
54.3656° N, 10.1423° E
Area
Baltic Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0 kn
Course
207°
Heading
104°
54.3656° N, 10.1423° E
Open the full live map →

Last 30 days: 10 port calls (Holtenau, Budelsdorf, Kiel Canal, Hamburg, Brunsbuttel, Sankt Margarethen, and Kiel).

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
Bianca Rambow
IMO numberWhat is an IMO number?
9297591
MMSIWhat is an MMSI?
211141000
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
9,981
Length overall
134 m
Beam
22.5 m
Year built
2004

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 years 2024–2025 · 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
Arrived at HoltenauAIS-detectedVoydar port-call detector (AIS geofence)
Left BudelsdorfAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BudelsdorfAIS-detectedVoydar port-call detector (AIS geofence)
Left Kiel CanalAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Kiel CanalAIS-detectedVoydar port-call detector (AIS geofence)

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
201814,040 t4,459 t180 days240 kg
201913,336 t4,215 t172 days262 kg
202013,461 t4,254 t166 days250 kg
202113,402 t4,213 t163 days263 kg
202212,049 t3,811 t148 days265 kg
202314,514 t4,610 t182 days255 kg
202412,834 t4,033 t163 days239 kg
202510,837 t3,441 t147 days230 kg

Technical efficiency: EEXI (24.69 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 4, 2026, 00:50 UTCin port—
Budelsdorf DEUSFOct 3, 2026, 20:54 UTCOct 3, 2026, 22:22 UTC1 h 28 min
Kiel Canal DECKLOct 3, 2026, 14:14 UTCOct 3, 2026, 16:19 UTC2 h 5 min
Hamburg DEHAMOct 2, 2026, 01:45 UTCOct 3, 2026, 10:38 UTC32 h 53 min
Brunsbuttel DEBRBSep 30, 2026, 21:49 UTCSep 30, 2026, 22:49 UTC59 min
Holtenau DEHTUSep 30, 2026, 10:40 UTCSep 30, 2026, 14:15 UTC3 h 35 min
Sankt Margarethen DESMASep 25, 2026, 22:46 UTCSep 25, 2026, 23:33 UTC47 min
Kiel Canal DECKLSep 25, 2026, 17:17 UTCSep 25, 2026, 22:15 UTC4 h 58 min
Hamburg DEHAMSep 23, 2026, 08:20 UTCSep 24, 2026, 09:42 UTC25 h 22 min
Kiel DEKELSep 22, 2026, 18:02 UTCSep 22, 2026, 19:58 UTC1 h 57 min
Altenwerder DEHHVAug 26, 2026, 10:56 UTCSep 2, 2026, 06:23 UTC6 d 19 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
Oct 3, 2026, 10:14 UTC
Draught change

Reported draught went from 8.1 m to 8.6 m while in port at Hamburg. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 1, 2026, 16:34 UTC
Draught change

Reported draught went from 8.6 m to 8 m after leaving Brunsbuttel. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)
Sep 24, 2026, 08:30 UTC
Draught change

Reported draught went from 8.7 m to 7.9 m while in port at Hamburg. 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 Bianca Rambow now?
Bianca Rambow (Container ship, Germany flag) was last seen on AIS on Oct 4, 2026, 02:03 UTC, not moving, in the port of Holtenau. The crew-entered destination was SEHEL (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 01:12 UTC). This report does not confirm the ship’s current route.
What kind of ship is Bianca Rambow?
Bianca Rambow is a container ship sailing under the flag of Germany, built in 2004 by Pella Sietas. The vessel is 134 m long with a beam of 22.5 m and has a gross tonnage of 9,981.
Who is recorded as the owner or manager of Bianca Rambow?
Reederei Rambow GmbH & Co. KG MS “Bianca Rambow” is recorded as ISM manager for Bianca Rambow (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for Bianca Rambow?
Voydar has no matched sanctions record displayed for Bianca Rambow 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 Bianca Rambow. 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/9297591
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