BIZTRAC BETA
Rental and operating of own or leased real estate

IMERSLUND HOLDING AS

Org. no. 994251651 Limited company (AS) Hamar Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 776,000
Equity NOK 33.5m
Incorporated 2009
Share capital NOK 200,000

IMERSLUND HOLDING AS is registered as a limited company in Hamar, Innlandet with organisation number 994251651. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Eie, leie og utvikle eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 776,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 776,000
Equity
NOK 33.5m
Est. value
NOK 25.2m

Financial health · 2024

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

Who owns IMERSLUND HOLDING AS?

OLE-MORTEN SVENKERUD
IMERSLUND HOLDING AS
NOK 1.3m rev. · NOK 776,000 profit

IMERSLUND HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does IMERSLUND HOLDING AS own?

IMERSLUND HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about IMERSLUND HOLDING AS

Who owns IMERSLUND HOLDING AS?

OLE-MORTEN SVENKERUD is the largest registered owner, with 100.0%.

What is the revenue of IMERSLUND HOLDING AS?

IMERSLUND HOLDING AS had revenue of NOK 1.3m in 2024.

Who is the general manager of IMERSLUND HOLDING AS?

Ole-Morten Svenkerud is registered as general manager of IMERSLUND HOLDING AS.

Where is IMERSLUND HOLDING AS based?

IMERSLUND HOLDING AS has its business address in Ingeberg.

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.