biztrac. BETA
COMPANY REGISTER PROFILE
928154289 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

ORO STOKKAMYR EIENDOM AS

Org. no. 928154289 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 54.6m
Operating profit NOK 46.2m
Equity NOK 144.6m
Incorporated 2021
Share capital NOK 140,000

ORO STOKKAMYR EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 928154289. 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 140,000, divided into 140000 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 2025 financial year, show NOK 54.6m in revenue and NOK 46.2m in operating profit.

Former names: ORO 12 AS

Key figures · 2025

Revenue
NOK 54.6m
▲ +3 %
Operating profit
NOK 46.2m
▲ +4 %
Equity
NOK 144.6m
▲ +12 %
Est. value
NOK 173.6m

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
7.2%
Satisfactory
Return on total assets
Solidity
22.8%
Good
Equity as a share of total capital

Who owns ORO STOKKAMYR EIENDOM AS?

ORO STOKKAMYR EIENDOM AS
NOK 54.6m rev. · NOK 46.2m profit

ORO STOKKAMYR EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ORO STOKKAMYR EIENDOM AS

Who owns ORO STOKKAMYR EIENDOM AS?

ORO STOKKAMYR AS is the largest registered owner, with 100.0%.

What is the revenue of ORO STOKKAMYR EIENDOM AS?

ORO STOKKAMYR EIENDOM AS had revenue of NOK 54.6m in 2025.

Where is ORO STOKKAMYR EIENDOM AS based?

ORO STOKKAMYR 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.