BIZTRAC BETA
Other captive investment companies

ROA INVEST AS

Org. no. 920497896 Limited company (AS) Kristiansund Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 355,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

ROA INVEST AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 920497896. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i næringsvirksomhet, aksjer og andeler, herunder deltakelse i andre selskaper med lignende virksomhet, samt å yte konsulenttjenester og leie ut arbeidskraft.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 355,000
Est. value
NOK 324,000

Financial health · 2025

Liquidity
-60260.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns ROA INVEST AS?

REIDAR ODDBJØRN ALSVIK
ROA INVEST AS
NOK 0 rev. · NOK −6,000 profit

ROA INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ROA INVEST AS own?

ROA INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ROA INVEST AS

Who owns ROA INVEST AS?

REIDAR ODDBJØRN ALSVIK is the largest registered owner, with 100.0%.

What is the revenue of ROA INVEST AS?

ROA INVEST AS had revenue of NOK 0 in 2025.

Where is ROA INVEST AS based?

ROA INVEST AS has its business address in Kristiansund N.

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.