BIZTRAC BETA
Rental and operating of own or leased real estate

MIKLAGARD PROPERTIES AS

Org. no. 820924762 Limited company (AS) Bærum Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 63.1m
Operating profit NOK 21.6m
Equity NOK 238.2m
Incorporated 2018
Share capital NOK 56,000

MIKLAGARD PROPERTIES AS is registered as a limited company in Bærum, Akershus with organisation number 820924762. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 56,000, divided into 100 shares. The company's stated purpose is: “Hotell-, og restaurantdrift, kjøp, salg og utleie av fast eiendom samt alt som naturlig står i forbindelse med dette, derunder investeringer og deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 63.1m in revenue and NOK 21.6m in operating profit.

Key figures · 2024

Revenue
NOK 63.1m
Operating profit
NOK 21.6m
Equity
NOK 238.2m
Est. value
NOK 195.3m

Financial health · 2024

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

Who owns MIKLAGARD PROPERTIES AS?

MIKLAGARD PROPERTIES HOLDING AS
MIKLAGARD PROPERTIES AS
NOK 63.1m rev. · NOK 21.6m profit

MIKLAGARD PROPERTIES AS has 1 registered shareholder:

All shareholders and roles →

Group structure

MIKLAGARD PROPERTIES AS er morselskap for 1 datterselskap:

Frequently asked questions about MIKLAGARD PROPERTIES AS

Who owns MIKLAGARD PROPERTIES AS?

MIKLAGARD PROPERTIES HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MIKLAGARD PROPERTIES AS?

MIKLAGARD PROPERTIES AS had revenue of NOK 63.1m in 2024.

Where is MIKLAGARD PROPERTIES AS based?

MIKLAGARD PROPERTIES 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.