BIZTRAC BETA
Rental and operating of own or leased real estate

IMA EIENDOM AS

Org. no. 991516603 Limited company (AS) Storfjord Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 268,000
Operating profit NOK −45,000
Equity NOK 161,000
Incorporated 2007
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−45k kr).

IMA EIENDOM AS is registered as a limited company in Storfjord, Troms with organisation number 991516603. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eie, drift, utleie og utvikling av fast eiendom og driftstilbehør. Samt utleie av parkeringsareal, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 268,000 in revenue and NOK −45,000 in operating profit.

Key figures · 2025

Revenue
NOK 268,000
Operating profit
NOK −45,000
Equity
NOK 161,000
Est. value
NOK 477,000

Financial health · 2025

Liquidity
0.15
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.2%
Weak
Equity as a share of total capital

Who owns IMA EIENDOM AS?

IMA HOLDING AS
IMA EIENDOM AS
NOK 268,000 rev. · NOK −45,000 profit

IMA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IMA EIENDOM AS

Who owns IMA EIENDOM AS?

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

What is the revenue of IMA EIENDOM AS?

IMA EIENDOM AS had revenue of NOK 268,000 in 2025.

Who is the general manager of IMA EIENDOM AS?

Rolf Ole Steinvik is registered as general manager of IMA EIENDOM AS.

Where is IMA EIENDOM AS based?

IMA EIENDOM AS has its business address in Oteren.

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.