BIZTRAC BETA
Development of building projects

ORA EIENDOM AS

Org. no. 931026925 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −492,000
Equity NOK −621,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

ORA EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 931026925. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg, drift og utvikling av fast eiendom, i tillegg til deltagelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −492,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −492,000
Equity
NOK −621,000

Financial health · 2024

Liquidity
5.50
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-20.6%
Weak
Equity as a share of total capital

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

Who owns ORA EIENDOM AS?

ORA AS
ORA EIENDOM AS
NOK 0 rev. · NOK −492,000 profit

ORA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ORA EIENDOM AS own?

ORA EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ORA EIENDOM AS

Who owns ORA EIENDOM AS?

ORA AS is the largest registered owner, with 100.0%.

What is the revenue of ORA EIENDOM AS?

ORA EIENDOM AS had revenue of NOK 0 in 2024.

Where is ORA EIENDOM AS based?

ORA EIENDOM AS has its business address in Trondheim.

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.