BIZTRAC BETA
Rental and operating of own or leased real estate

REM MARINE AS

Org. no. 839611722 Limited company (AS) Herøy Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 2.6m
Operating profit NOK 1.4m
Equity NOK 1.8m
Incorporated 1986
Share capital NOK 1.3m

REM MARINE AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 839611722. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1986. Registered share capital is NOK 1.3m, divided into 9000 shares. The company's stated purpose is: “Kjøp og salg av skipsrekvisita, utleie av lokaler, sjøhus og kaier, konsulenttjenester, formidling av båter, skipskontrakter, utførelse av reparasjonsarbeid og annen virksomhet som naturlig står et maritimt mmiljø i forbindelse, samt investere i eiendom og andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.6m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 2.6m
Operating profit
NOK 1.4m
Equity
NOK 1.8m
Est. value
NOK 2.2m

Financial health · 2024

Liquidity
40.17
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.9%
Weak
Equity as a share of total capital

Who owns REM MARINE AS?

SR MARINE II AS
REM MARINE AS
NOK 2.6m rev. · NOK 1.4m profit

REM MARINE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about REM MARINE AS

Who owns REM MARINE AS?

SR MARINE II AS is the largest registered owner, with 50.0%.

What is the revenue of REM MARINE AS?

REM MARINE AS had revenue of NOK 2.6m in 2024.

Who is the general manager of REM MARINE AS?

Tore Knut Remøy is registered as general manager of REM MARINE AS.

Where is REM MARINE AS based?

REM MARINE AS has its business address in Fosnavåg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.