BIZTRAC BETA
Rental and operating of own or leased real estate

MERLIN EIENDOM AS

Org. no. 993024619 Limited company (AS) Verdal Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 9.9m
Operating profit NOK 5.8m
Equity NOK 11.2m
Incorporated 2008
Share capital NOK 500,000

MERLIN EIENDOM AS is registered as a limited company in Verdal, Trøndelag with organisation number 993024619. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Selskapets formål er å drive kjøp, salg og utleie av fast eiendom og det som naturlig følger med slik virksomhet, samt deltakelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.9m in revenue and NOK 5.8m in operating profit.

Key figures · 2024

Revenue
NOK 9.9m
Operating profit
NOK 5.8m
Equity
NOK 11.2m
Est. value
NOK 21.1m

Financial health · 2024

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

Who owns MERLIN EIENDOM AS?

MERLIN AS
MERLIN EIENDOM AS
NOK 9.9m rev. · NOK 5.8m profit

MERLIN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

MERLIN EIENDOM AS er morselskap for 9 datterselskaper:

Frequently asked questions about MERLIN EIENDOM AS

Who owns MERLIN EIENDOM AS?

MERLIN AS is the largest registered owner, with 100.0%.

What is the revenue of MERLIN EIENDOM AS?

MERLIN EIENDOM AS had revenue of NOK 9.9m in 2024.

Who is the general manager of MERLIN EIENDOM AS?

Morten Skaufel is registered as general manager of MERLIN EIENDOM AS.

Where is MERLIN EIENDOM AS based?

MERLIN EIENDOM AS has its business address in Verdal.

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.