BIZTRAC BETA
Construction of residential and non-residential buildings

VESTFOLD BLÅSEISOLERING AS

Org. no. 931168681 Limited company (AS) Holmestrand Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 4.5m
Operating profit NOK 665,000
Equity NOK 666,000
Incorporated 2023
Share capital NOK 100,000

VESTFOLD BLÅSEISOLERING AS is registered as a limited company in Holmestrand, Vestfold with organisation number 931168681. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Salg av varer og tjenester knyttet til blåseisolering.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.5m in revenue and NOK 665,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.5m
Operating profit
NOK 665,000
Equity
NOK 666,000
Est. value
NOK 2.2m

Financial health · 2024

Liquidity
1.75
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.2%
Good
Equity as a share of total capital

Who owns VESTFOLD BLÅSEISOLERING AS?

RK VALEN HOLDING AS
VESTFOLD BLÅSEISOLERING AS
NOK 4.5m rev. · NOK 665,000 profit

VESTFOLD BLÅSEISOLERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTFOLD BLÅSEISOLERING AS

Who owns VESTFOLD BLÅSEISOLERING AS?

RK VALEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of VESTFOLD BLÅSEISOLERING AS?

VESTFOLD BLÅSEISOLERING AS had revenue of NOK 4.5m in 2024.

Who is the general manager of VESTFOLD BLÅSEISOLERING AS?

Rune Christian Hatlehol Valen is registered as general manager of VESTFOLD BLÅSEISOLERING AS.

Where is VESTFOLD BLÅSEISOLERING AS based?

VESTFOLD BLÅSEISOLERING AS has its business address in Holmestrand.

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.