BIZTRAC BETA
Rental and operating of own or leased real estate

OAK MANAGEMENT AS

Org. no. 944622934 Limited company (AS) Oslo Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 26.4m
Operating profit NOK 20.2m
Equity NOK 516.7m
Incorporated 1987
Share capital NOK 18.9m

OAK MANAGEMENT AS is registered as a limited company in Oslo, Oslo with organisation number 944622934. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 18.9m, divided into 37858 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder å eie og forvalte aksjer, verdipapirer, fast eiendom, og andre formuesverdier, deltagelse i andre selskaper, samt hva herved står i forbindelse, og rådgivning på de samme områder.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.4m in revenue and NOK 20.2m in operating profit.

Key figures · 2024

Revenue
NOK 26.4m
Operating profit
NOK 20.2m
Equity
NOK 516.7m
Est. value
NOK 407.2m

Financial health · 2024

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

Who owns OAK MANAGEMENT AS?

TACONIC AS
OAK MANAGEMENT AS
NOK 26.4m rev. · NOK 20.2m profit

OAK MANAGEMENT AS has 2 registered shareholders:

All shareholders and roles →

Which companies does OAK MANAGEMENT AS own?

OAK MANAGEMENT AS holds stakes in 10 companies:

See the full ownership structure →

Frequently asked questions about OAK MANAGEMENT AS

Who owns OAK MANAGEMENT AS?

TACONIC AS is the largest registered owner, with 97.0%.

What is the revenue of OAK MANAGEMENT AS?

OAK MANAGEMENT AS had revenue of NOK 26.4m in 2024.

Where is OAK MANAGEMENT AS based?

OAK MANAGEMENT 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.