Skip to content

Ro Server

Cargo ship · Norway · built 2016 · AIS Class A

IMO9773260MMSI258534000Call signLDRCLast AIS position Oct 1, 2026, 21:13 UTC

In short

Ro Server (Cargo ship, Norway flag) was last seen on AIS on , not moving, in the Norwegian Sea. Its crew-entered AIS destination is CH 16 FISHFARMS; its reported draught is 7.2 m (voyage report via BarentsWatch AIS API, received Oct 1, 2026, 20:51 UTC). Registered owner: Rostein (source: Wikidata).

Current voyage: from Svelgen (departed Sep 30, 2026, 17:59 UTC) to CH 16 FISHFARMS

Vessel type
Cargo ship
Flag
Norway
Year built
2016
Gross tonnage
3,579
Size (length × beam)
82 m × 16 m
Registered owner
Rostein

Watch this ship

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

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 RO SERVER
Photo: Cavernia · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
61.6037° N, 5.1858° E
Area
Norwegian Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0 kn
Course
16°
Heading
308°
61.6037° N, 5.1858° E
Open the full live map →

Last 30 days: at least 12 port calls (Svelgen, Storoya, Solund, Floro, Steinshamn, Flora, and Fusa).

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
Ro Server
IMO numberWhat is an IMO number?
9773260
MMSIWhat is an MMSI?
258534000
Flag
Norway
Vessel type
Cargo ship
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
3,579
Length overall
82.1 m
Beam
15.5 m
Year built
2016

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
Operator
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 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 SvelgenAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at SvelgenAIS-detectedVoydar port-call detector (AIS geofence)
Left SvelgenAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at SvelgenAIS-detectedVoydar port-call detector (AIS geofence)
Left StoroyaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at StoroyaAIS-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.

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
Svelgen NOSVESep 30, 2026, 16:03 UTCSep 30, 2026, 17:59 UTC1 h 56 min
Svelgen NOSVESep 28, 2026, 17:42 UTCSep 28, 2026, 21:07 UTC3 h 25 min
Storoya NOSOYSep 27, 2026, 03:51 UTCSep 27, 2026, 15:29 UTC11 h 39 min
Storoya NOSOYSep 25, 2026, 04:11 UTCSep 25, 2026, 18:29 UTC14 h 18 min
Solund NOSLDSep 22, 2026, 09:23 UTCSep 22, 2026, 23:00 UTC13 h 37 min
Solund NOSLDSep 22, 2026, 02:44 UTCSep 22, 2026, 09:22 UTC6 h 37 min
Solund NOSLDSep 21, 2026, 16:30 UTCSep 22, 2026, 02:43 UTC10 h 13 min
Floro NOFROSep 14, 2026, 14:32 UTCSep 14, 2026, 15:06 UTC34 min
Steinshamn NOSTHSep 12, 2026, 15:12 UTCSep 12, 2026, 21:43 UTC6 h 31 min
Flora NOFLRSep 11, 2026, 01:15 UTCSep 11, 2026, 10:08 UTC8 h 53 min
Flora NOFLRSep 9, 2026, 07:33 UTCSep 9, 2026, 08:09 UTC36 min
Fusa NOFUSSep 4, 2026, 18:49 UTCSep 5, 2026, 16:29 UTC21 h 40 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 Ro Server now?
Ro Server (Cargo ship, Norway flag) was last seen on AIS on Oct 1, 2026, 21:13 UTC, not moving, in the Norwegian Sea. The crew-entered destination was CH 16 FISHFARMS (voyage report via BarentsWatch AIS API, received Oct 1, 2026, 20:51 UTC). This report does not confirm the ship’s current route.
What kind of ship is Ro Server?
Ro Server is a cargo ship sailing under the flag of Norway, built in 2016 by Larsnes Mekaniske Verkstad. The vessel is 82.1 m long with a beam of 15.5 m and has a gross tonnage of 3,579.
Who is recorded as the owner or manager of Ro Server?
Rostein is recorded as Registered owner for Ro Server (source: Wikidata). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for Ro Server?
Voydar has no matched sanctions record displayed for Ro Server from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Ro Server. 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/9773260
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