BIZTRAC BETA
Buying and selling of own real estate

I-3 EIENDOM AS

Org. no. 998681111 Limited company (AS) Enebakk Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −1,000
Equity NOK −253,000
Incorporated 2012
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−253k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1k kr).

I-3 EIENDOM AS is registered as a limited company in Enebakk, Akershus with organisation number 998681111. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av fast eiendom, utleie og drift av fast eiendom, anleggsvirksomhet, investeringsvirksomhet, deltakelse i andre selskaper, samt alt hva som kommer inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK −253,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns I-3 EIENDOM AS?

ME & MO HOLDING AS
I-3 EIENDOM AS
NOK 0 rev. · NOK −1,000 profit

I-3 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about I-3 EIENDOM AS

Who owns I-3 EIENDOM AS?

ME & MO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of I-3 EIENDOM AS?

I-3 EIENDOM AS had revenue of NOK 0 in 2024.

Where is I-3 EIENDOM AS based?

I-3 EIENDOM AS has its business address in Ytre Enebakk.

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.