Skip to content

Ro Chief

Other · Norway · built 2002 · AIS Class A

IMO9267596MMSI258375000Call signLLVULast AIS position Oct 3, 2026, 00:10 UTC

In short

Ro Chief (Other, Norway flag) was last seen on AIS on , not moving, in the port of Lodingen. Its crew-entered AIS destination is CH 16; its reported draught is 5.5 m (voyage report via BarentsWatch AIS API, received Oct 2, 2026, 23:47 UTC). It arrived there on Oct 2, 2026, 20:28 UTC. Registered owner: Rostein (source: Wikidata).

Vessel type
Other
Flag
Norway
Year built
2002
Gross tonnage
1,066
Size (length × beam)
53 m × 12 m
Registered owner
Rostein

Watch this ship

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

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 CHIEF
Photo: Trondheim Havn from Trondheim, Norway · Licence: CC BY-SA 2.0 · via Wikimedia Commons

Last reported position

received
Position
68.4144° N, 15.9975° E
Area
Norwegian Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0 kn
Course
121°
Heading
207°
68.4144° N, 15.9975° E
Open the full live map →

Last 30 days: 8 port calls (Lodingen, Vagaholmen, Mo i Rana, Harstad, Bogoy, and Tromso).

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 Chief
IMO numberWhat is an IMO number?
9267596
MMSIWhat is an MMSI?
258375000
Flag
Norway
Vessel type
Other
Gross tonnageGross tonnage vs deadweight
1,066
Length overall
53 m
Beam
12 m
Year built
2002

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
Arrived at LodingenAIS-detectedVoydar port-call detector (AIS geofence)
Left VagaholmenAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at VagaholmenAIS-detectedVoydar port-call detector (AIS geofence)
Left Mo i RanaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Mo i RanaAIS-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
Lodingen NOLODOct 2, 2026, 20:28 UTCin port—
Vagaholmen NOVOHOct 1, 2026, 10:53 UTCOct 1, 2026, 11:44 UTC51 min
Mo i Rana NOMQNSep 30, 2026, 19:55 UTCOct 1, 2026, 02:47 UTC6 h 52 min
Mo i Rana NOMQNSep 29, 2026, 15:40 UTCSep 30, 2026, 11:27 UTC19 h 47 min
Harstad NOHRDSep 22, 2026, 07:47 UTCSep 28, 2026, 11:25 UTC6 d 3 h
Bogoy NOOYBSep 17, 2026, 15:11 UTCSep 17, 2026, 17:04 UTC1 h 53 min
Tromso NOTOSSep 7, 2026, 01:59 UTCSep 7, 2026, 17:42 UTC15 h 43 min
Bogoy NOOYBSep 5, 2026, 17:25 UTCSep 6, 2026, 09:11 UTC15 h 46 min
Bodo NOBOOSep 1, 2026, 16:10 UTCSep 2, 2026, 02:05 UTC9 h 55 min
Melkoya NOMLKAug 20, 2026, 16:34 UTCAug 22, 2026, 09:16 UTC40 h 42 min
Hammerfest NOHFTAug 17, 2026, 11:18 UTCAug 19, 2026, 17:52 UTC2 d 6 h
Melkoya NOMLKAug 9, 2026, 04:29 UTCAug 9, 2026, 07:58 UTC3 h 29 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 Chief now?
Ro Chief (Other, Norway flag) was last seen on AIS on Oct 3, 2026, 00:10 UTC, not moving, in the port of Lodingen. The crew-entered destination was CH 16 (voyage report via BarentsWatch AIS API, received Oct 2, 2026, 23:47 UTC). This report does not confirm the ship’s current route.
What kind of ship is Ro Chief?
Ro Chief is a other sailing under the flag of Norway, built in 2002 by Aas Mek. Verksted AS. The vessel is 53 m long with a beam of 12 m and has a gross tonnage of 1,066.
Who is recorded as the owner or manager of Ro Chief?
Rostein is recorded as Registered owner for Ro Chief (source: Wikidata). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for Ro Chief?
Voydar has no matched sanctions record displayed for Ro Chief 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 Chief. 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/9267596
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