BIZTRAC BETA
Rental and operating of own or leased real estate

ØSTAFJELLS EIENDOM AS

Org. no. 928458954 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −93,000
Equity NOK 64.1m
Incorporated 2021
Share capital NOK 660,000

Signals

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

ØSTAFJELLS EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 928458954. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 660,000, divided into 6600 shares. The company's stated purpose is: “Oppkjøp og forvaltning av næringseiendom, samt virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −93,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −93,000
Equity
NOK 64.1m
Est. value
NOK 58.5m

Financial health · 2024

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

Who owns ØSTAFJELLS EIENDOM AS?

UTBYTTE AS
ØSTAFJELLS EIENDOM AS
NOK 0 rev. · NOK −93,000 profit

ØSTAFJELLS EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ØSTAFJELLS EIENDOM AS own?

ØSTAFJELLS EIENDOM AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about ØSTAFJELLS EIENDOM AS

Who owns ØSTAFJELLS EIENDOM AS?

UTBYTTE AS is the largest registered owner, with 51.0%.

What is the revenue of ØSTAFJELLS EIENDOM AS?

ØSTAFJELLS EIENDOM AS had revenue of NOK 0 in 2024.

Where is ØSTAFJELLS EIENDOM AS based?

ØSTAFJELLS 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.