BIZTRAC BETA
Rental and operating of own or leased real estate

EIKELI EIENDOM AS

Org. no. 921674562 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK −86,000
Equity NOK −22.7m
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−22,7 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−86k kr).

EIKELI EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 921674562. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie av fast eiendom og eiendomsutvikling samt direkte og indirekte deltakelse i selskaper med lignende eller annet formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK −86,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK −86,000
Equity
NOK −22.7m

Financial health · 2024

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

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

Who owns EIKELI EIENDOM AS?

EIKELI BOLIGINVEST AS
EIKELI EIENDOM AS
NOK 2.5m rev. · NOK −86,000 profit

EIKELI EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIKELI EIENDOM AS

Who owns EIKELI EIENDOM AS?

EIKELI BOLIGINVEST AS is the largest registered owner, with 100.0%.

What is the revenue of EIKELI EIENDOM AS?

EIKELI EIENDOM AS had revenue of NOK 2.5m in 2024.

Where is EIKELI EIENDOM AS based?

EIKELI EIENDOM 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.