Skip to content

REM FORTRESS

Other · Cyprus · built 2011 · AIS Class A

IMO9482342MMSI209455000Call sign5BFR3Last AIS position Oct 6, 2026, 11:14 UTC

In short

REM FORTRESS (Other, Cyprus flag) was last seen on AIS on , not moving, in the Baltic Sea. Its crew-entered AIS destination is OFF SCHONHAGEN; its reported draught is 5.5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 11:03 UTC). Registered owner: K Line Offshore AS (source: Wikidata).

Current voyage: from Holtenau (departed Oct 3, 2026, 14:51 UTC) to OFF SCHONHAGEN

Vessel type
Other
Flag
Cyprus
Year built
2011
Gross tonnage
4,518
Size (length × beam)
94 m
Registered owner
K Line Offshore AS

Watch this ship

Get an email when REM FORTRESS arrives or 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 KL Brisfjord
Photo: Alan Jamieson from Aberdeen, Scotland · Licence: CC BY 2.0 · via Wikimedia Commons

Last reported position

received
Position
54.6123° N, 10.0999° E
Area
Baltic Sea
StatusWhat do AIS statuses mean?
Restricted manoeuvrability
Speed
0 kn
Course
23°
Heading
19°
54.6123° N, 10.0999° E
Open the full live map →

Last 30 days: 3 port calls (Holtenau, Kiel Canal, and Aberdeen).

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
REM FORTRESS
IMO numberWhat is an IMO number?
9482342
MMSIWhat is an MMSI?
209455000
Call signWhat is a call sign?
5BFR3
Flag
Cyprus
Vessel type
Other
Gross tonnageGross tonnage vs deadweight
4,518
Length overall
94 m
Beam
—
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.

Registered owner
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Oct 5, 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 HoltenauAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at HoltenauAIS-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)
Left AberdeenAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at AberdeenAIS-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
20252,511 t783 t138 days400 kg

Technical efficiency: Not Applicable. 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 3, 2026, 13:43 UTCOct 3, 2026, 14:51 UTC1 h 8 min
Kiel Canal DECKLOct 3, 2026, 03:25 UTCOct 3, 2026, 05:43 UTC2 h 18 min
Aberdeen GBABDSep 25, 2026, 09:21 UTCSep 25, 2026, 13:48 UTC4 h 27 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.

Frequently asked questions

Where is REM FORTRESS now?
REM FORTRESS (Other, Cyprus flag) was last seen on AIS on Oct 6, 2026, 11:14 UTC, not moving, in the Baltic Sea. The crew-entered destination was OFF SCHONHAGEN (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 11:03 UTC). This report does not confirm the ship’s current route.
What kind of ship is REM FORTRESS?
REM FORTRESS is a other sailing under the flag of Cyprus, built in 2011 by Trosvik Verksted. The vessel is 94 m long and has a gross tonnage of 4,518.
Who is recorded as the owner or manager of REM FORTRESS?
K Line Offshore AS is recorded as Registered owner for REM FORTRESS (source: Wikidata). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for REM FORTRESS?
Voydar has no matched sanctions record displayed for REM FORTRESS 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 REM FORTRESS. 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/9482342
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