BIZTRAC BETA
Rental and operating of own or leased real estate

VAALA BRUK EIENDOM AS

Org. no. 932285827 Limited company (AS) Ringebu Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK 5.2m
Equity NOK 4.0m
Incorporated 2023
Share capital NOK 30,000

VAALA BRUK EIENDOM AS is registered as a limited company in Ringebu, Innlandet with organisation number 932285827. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom kjøp og salg av maskiner og utstyr, drive med maskin entreprenørtjenester og dets like. Videre kan virksomheten bestå av deltakelse i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK 5.2m in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK 5.2m
Equity
NOK 4.0m
Est. value
NOK 13.0m

Financial health · 2024

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

Who owns VAALA BRUK EIENDOM AS?

KNUT KVITRUD AS
VAALA BRUK EIENDOM AS
NOK 5.3m rev. · NOK 5.2m profit

VAALA BRUK EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about VAALA BRUK EIENDOM AS

Who owns VAALA BRUK EIENDOM AS?

KNUT KVITRUD AS is the largest registered owner, with 35.3%.

What is the revenue of VAALA BRUK EIENDOM AS?

VAALA BRUK EIENDOM AS had revenue of NOK 5.3m in 2024.

Where is VAALA BRUK EIENDOM AS based?

VAALA BRUK EIENDOM AS has its business address in Ringebu.

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.