BIZTRAC BETA
Site preparation

ROAR WILHELMSEN INVEST AS

Org. no. 922768080 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −71,000
Equity NOK 14.5m
Incorporated 2019
Share capital NOK 201,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−71k kr).
  • Nylig endring 2026-03-28 Aksjekapital registrert 2026-03-28.

ROAR WILHELMSEN INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 922768080. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2019. Registered share capital is NOK 201,000, divided into 101 shares. The company's stated purpose is: “Investering i verdipapirer, fast eiendom og tilhørende virksomhet.”.

Key figures · 2024

Operating profit
NOK −71,000
Equity
NOK 14.5m
Est. value
NOK 14.8m

Financial health · 2024

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

Who owns ROAR WILHELMSEN INVEST AS?

ANDERS WILHELMSEN
ROAR WILHELMSEN INVEST AS
· NOK −71,000 profit

ROAR WILHELMSEN INVEST AS has 5 registered shareholders:

All shareholders and roles →

Which companies does ROAR WILHELMSEN INVEST AS own?

ROAR WILHELMSEN INVEST AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

ROAR WILHELMSEN INVEST AS er morselskap for 5 datterselskaper:

Frequently asked questions about ROAR WILHELMSEN INVEST AS

Who owns ROAR WILHELMSEN INVEST AS?

ANDERS WILHELMSEN is the largest registered owner, with 49.0%.

Who is the general manager of ROAR WILHELMSEN INVEST AS?

Hans Roar Slattum Wilhelmsen is registered as general manager of ROAR WILHELMSEN INVEST AS.

Where is ROAR WILHELMSEN INVEST AS based?

ROAR WILHELMSEN INVEST AS has its business address in Oslo.

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.