BIZTRAC BETA
Development of building projects

KLOSTERØYA VEST AS

Org. no. 997456637 Limited company (AS) Skien Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 37.4m
Operating profit NOK −726,000
Equity NOK 53.9m
Incorporated 2011
Share capital NOK 942,000

Signals

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

KLOSTERØYA VEST AS is registered as a limited company in Skien, Telemark with organisation number 997456637. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2011. Registered share capital is NOK 942,000, divided into 47094 shares. The company's stated purpose is: “Investering i aksjer og andre eierandeler i andre selskaper og foretak, samt all annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 37.4m in revenue and NOK −726,000 in operating profit.

Key figures · 2025

Revenue
NOK 37.4m
Operating profit
NOK −726,000
Equity
NOK 53.9m
Est. value
NOK 92.7m

Financial health · 2025

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

Who owns KLOSTERØYA VEST AS?

CONCEPTOR BOLIG AS
KLOSTERØYA VEST AS
NOK 37.4m rev. · NOK −726,000 profit

KLOSTERØYA VEST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does KLOSTERØYA VEST AS own?

KLOSTERØYA VEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KLOSTERØYA VEST AS

Who owns KLOSTERØYA VEST AS?

CONCEPTOR BOLIG AS is the largest registered owner, with 37.3%.

What is the revenue of KLOSTERØYA VEST AS?

KLOSTERØYA VEST AS had revenue of NOK 37.4m in 2025.

Where is KLOSTERØYA VEST AS based?

KLOSTERØYA VEST 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.