BIZTRAC BETA
Uoppgitt

HENRIK ROSENVOLD INVEST AS

Org. no. 921882238 Limited company (AS) Skien Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 7.2m
Incorporated 2018
Share capital NOK 150,000

Signals

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

HENRIK ROSENVOLD INVEST AS is registered as a limited company in Skien, Telemark with organisation number 921882238. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 150,000, divided into 50 shares. The company's stated purpose is: “Å investere i aksjer og andre verdipapirer, samt annet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 7.2m
Est. value
NOK 8.9m

Financial health · 2025

Liquidity
4381.82
Very good
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 HENRIK ROSENVOLD INVEST AS?

HENRIK ROSENVOLD
HENRIK ROSENVOLD INVEST AS
NOK 0 rev. · NOK −5,000 profit

HENRIK ROSENVOLD INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HENRIK ROSENVOLD INVEST AS

Who owns HENRIK ROSENVOLD INVEST AS?

HENRIK ROSENVOLD is the largest registered owner, with 100.0%.

What is the revenue of HENRIK ROSENVOLD INVEST AS?

HENRIK ROSENVOLD INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of HENRIK ROSENVOLD INVEST AS?

Henrik Rosenvold is registered as general manager of HENRIK ROSENVOLD INVEST AS.

Where is HENRIK ROSENVOLD INVEST AS based?

HENRIK ROSENVOLD INVEST AS has its business address in Skien.

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.