BIZTRAC BETA
Rental and operating of own or leased real estate

ORO BREIVOLLBYEN AS

Org. no. 928726932 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −2.4m
Equity NOK 250.1m
Incorporated 2022
Share capital NOK 2.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,4 mill kr).

ORO BREIVOLLBYEN AS is registered as a limited company in Oslo, Oslo with organisation number 928726932. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 2.0m, divided into 1000000 shares. The company's stated purpose is: “Investere i eiendom og alt som står i forbindelse med dette, herunder deltakelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −2.4m in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −2.4m
Equity
NOK 250.1m
Est. value
NOK 228.2m

Financial health · 2024

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

Who owns ORO BREIVOLLBYEN AS?

KGJ REAL ESTATE AS
ORO BREIVOLLBYEN AS
NOK 0 rev. · NOK −2.4m profit

ORO BREIVOLLBYEN AS has 20 registered shareholders:

All shareholders and roles →

Which companies does ORO BREIVOLLBYEN AS own?

ORO BREIVOLLBYEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ORO BREIVOLLBYEN AS

Who owns ORO BREIVOLLBYEN AS?

KGJ REAL ESTATE AS is the largest registered owner, with 20.0%.

What is the revenue of ORO BREIVOLLBYEN AS?

ORO BREIVOLLBYEN AS had revenue of NOK 0 in 2024.

Where is ORO BREIVOLLBYEN AS based?

ORO BREIVOLLBYEN 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.