BIZTRAC BETA
Rental and operating of own or leased real estate

MIDGARD EIENDOM HOLDING AS

Org. no. 990480346 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 65.2m
Operating profit NOK 49.8m
Equity NOK 433.5m
Incorporated 2006
Share capital NOK 200,000

Signals

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

MIDGARD EIENDOM HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 990480346. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 200,000, divided into 1000 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 65.2m in revenue and NOK 49.8m in operating profit.

Key figures · 2024

Revenue
NOK 65.2m
Operating profit
NOK 49.8m
Equity
NOK 433.5m
Est. value
NOK 416.9m

Financial health · 2024

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

Who owns MIDGARD EIENDOM HOLDING AS?

KTP HOLDING I AS
MIDGARD EIENDOM HOLDING AS
NOK 65.2m rev. · NOK 49.8m profit

MIDGARD EIENDOM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIDGARD EIENDOM HOLDING AS

Who owns MIDGARD EIENDOM HOLDING AS?

KTP HOLDING I AS is the largest registered owner, with 100.0%.

What is the revenue of MIDGARD EIENDOM HOLDING AS?

MIDGARD EIENDOM HOLDING AS had revenue of NOK 65.2m in 2024.

Where is MIDGARD EIENDOM HOLDING AS based?

MIDGARD EIENDOM HOLDING AS has its business address in Oslo.

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.