Skip to content

RONJA HEROY

Other · Norway · AIS Class A

IMO9923188MMSI258112000Call signLGOCLast AIS position Oct 4, 2026, 15:09 UTC

In short

RONJA HEROY (Other, Norway flag) was last seen on AIS on , not moving, in the port of Bronnoysund. Its crew-entered AIS destination is FISHFARM; its reported draught is 8 m (voyage report via BarentsWatch AIS API, received Oct 4, 2026, 14:36 UTC). It arrived there on Oct 4, 2026, 13:47 UTC. ISM manager: Solvtrans Management AS (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Other
Flag
Norway
Year built
—
Gross tonnage
—
Size (length × beam)
—

Watch this ship

Get an email when RONJA HEROY 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 RONJA HEROY.

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.

Last reported position

received
Position
65.4933° N, 12.2226° E
Area
Baltic Sea
Speed
0 kn
Course
167°
Heading
23°
65.4933° N, 12.2226° E
Open the full live map →

Last 30 days: 4 port calls (Bronnoysund, Heroy, and Sandnessjoen).

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
RONJA HEROY
IMO numberWhat is an IMO number?
9923188
MMSIWhat is an MMSI?
258112000
Flag
Norway
Vessel type
Other
Length overall
—
Beam
—
Year built
—

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

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 BronnoysundAIS-detectedVoydar port-call detector (AIS geofence)
Left BronnoysundAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BronnoysundAIS-detectedVoydar port-call detector (AIS geofence)
Left HeroyAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at HeroyAIS-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
20247,163 t2,380 t250 days663 kg
20257,710 t2,712 t292 days624 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
Bronnoysund NOBNNOct 4, 2026, 13:47 UTCin port—
Bronnoysund NOBNNSep 27, 2026, 18:45 UTCSep 28, 2026, 22:17 UTC27 h 32 min
Heroy NOHROSep 27, 2026, 06:05 UTCSep 27, 2026, 10:40 UTC4 h 35 min
Sandnessjoen NOSSJSep 22, 2026, 14:48 UTCSep 23, 2026, 01:54 UTC11 h 7 min
Tromso NOTOSAug 23, 2026, 10:33 UTCAug 23, 2026, 12:55 UTC2 h 22 min
Bodo NOBOOAug 19, 2026, 10:36 UTCAug 19, 2026, 13:19 UTC2 h 43 min
Kvalvika NOKVVAug 19, 2026, 04:51 UTCAug 19, 2026, 10:36 UTC5 h 45 min
Vikholmen NOVHNJul 26, 2026, 18:09 UTCJul 30, 2026, 06:29 UTC3 d 12 h
Gutvik NOGUTJul 16, 2026, 20:51 UTCJul 17, 2026, 05:19 UTC8 h 27 min
Kvalvika NOKVVJul 11, 2026, 15:55 UTCJul 16, 2026, 20:48 UTC5 d 4 h
Tromso NOTOSJul 2, 2026, 18:35 UTCJul 3, 2026, 00:05 UTC5 h 30 min
Kvalvika NOKVVJun 16, 2026, 14:27 UTCJun 20, 2026, 07:26 UTC3 d 17 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.

Frequently asked questions

Where is RONJA HEROY now?
RONJA HEROY (Other, Norway flag) was last seen on AIS on Oct 4, 2026, 15:09 UTC, not moving, in the port of Bronnoysund. The crew-entered destination was FISHFARM (voyage report via BarentsWatch AIS API, received Oct 4, 2026, 14:36 UTC). This report does not confirm the ship’s current route.
What kind of ship is RONJA HEROY?
RONJA HEROY is a other sailing under the flag of Norway.
Who is recorded as the owner or manager of RONJA HEROY?
Solvtrans Management AS is recorded as ISM manager for RONJA HEROY (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 RONJA HEROY?
Voydar has no matched sanctions record displayed for RONJA HEROY 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 RONJA HEROY. 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/9923188
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