BIZTRAC BETA
Development of building projects

VESTRE SKANSEN AS

Org. no. 927047713 Limited company (AS) Askøy Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 12.1m
Operating profit NOK 347,000
Equity NOK 13.4m
Incorporated 2021
Share capital NOK 3.0m

VESTRE SKANSEN AS is registered as a limited company in Askøy, Vestland with organisation number 927047713. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 3.0m, divided into 1000 shares. The company's stated purpose is: “Erverv, drift, forvaltning, utvikling og salg av fast eiendom og alt som står i naturlig forbindelse med dette. Selskapet kan også gjennom aksjeerverv eller på annen måte, delta i og gjøre seg interessert i annen virksomhet, uansett formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.1m in revenue and NOK 347,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.1m
Operating profit
NOK 347,000
Equity
NOK 13.4m
Est. value
NOK 10.1m

Financial health · 2024

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

Who owns VESTRE SKANSEN AS?

HEFI INVEST AS
VESTRE SKANSEN AS
NOK 12.1m rev. · NOK 347,000 profit

VESTRE SKANSEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about VESTRE SKANSEN AS

Who owns VESTRE SKANSEN AS?

HEFI INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of VESTRE SKANSEN AS?

VESTRE SKANSEN AS had revenue of NOK 12.1m in 2024.

Who is the general manager of VESTRE SKANSEN AS?

Frode Kristensen is registered as general manager of VESTRE SKANSEN AS.

Where is VESTRE SKANSEN AS based?

VESTRE SKANSEN AS has its business address in Herdla.

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.