BIZTRAC BETA
Rental and operating of own or leased real estate

ELLE EIENDOM AS

Org. no. 931310550 Limited company (AS) Frogn Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 580,000
Operating profit NOK −290,000
Equity NOK 30.1m
Incorporated 2023
Share capital NOK 101,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−290k kr).

ELLE EIENDOM AS is registered as a limited company in Frogn, Akershus with organisation number 931310550. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 101,000, divided into 100000 shares. The company's stated purpose is: “Være ett holding selskap samt foreta investering i verdipapirer og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 580,000 in revenue and NOK −290,000 in operating profit.

Key figures · 2024

Revenue
NOK 580,000
Operating profit
NOK −290,000
Equity
NOK 30.1m
Est. value
NOK 26.2m

Financial health · 2024

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

Who owns ELLE EIENDOM AS?

NINA BRAATEN
ELLE EIENDOM AS
NOK 580,000 rev. · NOK −290,000 profit

ELLE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ELLE EIENDOM AS own?

ELLE EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ELLE EIENDOM AS

Who owns ELLE EIENDOM AS?

NINA BRAATEN is the largest registered owner, with 100.0%.

What is the revenue of ELLE EIENDOM AS?

ELLE EIENDOM AS had revenue of NOK 580,000 in 2024.

Where is ELLE EIENDOM AS based?

ELLE EIENDOM AS has its business address in Drøbak.

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.