BIZTRAC BETA
Rental and operating of own or leased real estate

ORO KARIHAUGVEIEN AS

Org. no. 825880992 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 22.0m
Operating profit NOK 14.5m
Equity NOK 127.7m
Incorporated 2020
Share capital NOK 2.6m

Signals

1 flags
  • Nylig endring 2026-06-08 Aksjekapital registrert 2026-06-08.

ORO KARIHAUGVEIEN AS is registered as a limited company in Oslo, Oslo with organisation number 825880992. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 2.6m, divided into 1281250 shares. The company's stated purpose is: “Investere i eiendom og alt som står iforbindelse med dette, herunder deltakelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 22.0m in revenue and NOK 14.5m in operating profit.

Key figures · 2025

Revenue
NOK 22.0m
Operating profit
NOK 14.5m
Equity
NOK 127.7m
Est. value
NOK 115.2m

Financial health · 2025

Liquidity
0.46
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.3%
Good
Equity as a share of total capital

Who owns ORO KARIHAUGVEIEN AS?

FILTBYGG AS
ORO KARIHAUGVEIEN AS
NOK 22.0m rev. · NOK 14.5m profit

ORO KARIHAUGVEIEN AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does ORO KARIHAUGVEIEN AS own?

ORO KARIHAUGVEIEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ORO KARIHAUGVEIEN AS

Who owns ORO KARIHAUGVEIEN AS?

FILTBYGG AS is the largest registered owner, with 16.0%.

What is the revenue of ORO KARIHAUGVEIEN AS?

ORO KARIHAUGVEIEN AS had revenue of NOK 22.0m in 2025.

Where is ORO KARIHAUGVEIEN AS based?

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