BIZTRAC BETA
Rental and operating of own or leased real estate

LYSAKER PARK EIENDOM AS

Org. no. 918905839 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 135.2m
Operating profit NOK 95.9m
Equity NOK 988.5m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LYSAKER PARK EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 918905839. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 135.2m in revenue and NOK 95.9m in operating profit.

Key figures · 2024

Revenue
NOK 135.2m
Operating profit
NOK 95.9m
Equity
NOK 988.5m
Est. value
NOK 914.3m

Financial health · 2024

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

Who owns LYSAKER PARK EIENDOM AS?

STOREBRAND AIF AS
LYSAKER PARK EIENDOM AS
NOK 135.2m rev. · NOK 95.9m profit

LYSAKER PARK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYSAKER PARK EIENDOM AS

Who owns LYSAKER PARK EIENDOM AS?

STOREBRAND AIF AS is the largest registered owner, with 100.0%.

What is the revenue of LYSAKER PARK EIENDOM AS?

LYSAKER PARK EIENDOM AS had revenue of NOK 135.2m in 2024.

Where is LYSAKER PARK EIENDOM AS based?

LYSAKER PARK EIENDOM AS has its business address in Lysaker.

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.