BIZTRAC BETA
Rental and operating of own or leased real estate

ROALKVAMHAGEN AS

Org. no. 927384337 Limited company (AS) Midt-Telemark Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 462,000
Operating profit NOK 161,000
Equity NOK −350,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−350k kr).

ROALKVAMHAGEN AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 927384337. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie av boliger og hybler, samt kjøp, utvikling og salg av faste eiendommer, herunder å eie aksjer i andre selskaper, samt alt som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 462,000 in revenue and NOK 161,000 in operating profit.

Key figures · 2024

Revenue
NOK 462,000
Operating profit
NOK 161,000
Equity
NOK −350,000
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-4.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ROALKVAMHAGEN AS?

JOHANNES FORBERG
ROALKVAMHAGEN AS
NOK 462,000 rev. · NOK 161,000 profit

ROALKVAMHAGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROALKVAMHAGEN AS

Who owns ROALKVAMHAGEN AS?

JOHANNES FORBERG is the largest registered owner, with 100.0%.

What is the revenue of ROALKVAMHAGEN AS?

ROALKVAMHAGEN AS had revenue of NOK 462,000 in 2024.

Where is ROALKVAMHAGEN AS based?

ROALKVAMHAGEN AS has its business address in Bø I Telemark.

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.