BIZTRAC BETA
Uoppgitt

OLAV AAKRE HOLDING AS

Org. no. 930036714 Limited company (AS) Skien Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −7,000
Equity NOK 31,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

OLAV AAKRE HOLDING AS is registered as a limited company in Skien, Telemark with organisation number 930036714. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Konsulentvirksomhet, investering og deltakelse i andre selskaper og det som derved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 31,000
Est. value
NOK 368,000

Financial health · 2024

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
55.8%
Weak
Equity as a share of total capital

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

Who owns OLAV AAKRE HOLDING AS?

OLAV AAKRE
OLAV AAKRE HOLDING AS
NOK 0 rev. · NOK −7,000 profit

OLAV AAKRE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OLAV AAKRE HOLDING AS own?

OLAV AAKRE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OLAV AAKRE HOLDING AS

Who owns OLAV AAKRE HOLDING AS?

OLAV AAKRE is the largest registered owner, with 100.0%.

What is the revenue of OLAV AAKRE HOLDING AS?

OLAV AAKRE HOLDING AS had revenue of NOK 0 in 2024.

Where is OLAV AAKRE HOLDING AS based?

OLAV AAKRE HOLDING AS has its business address in Skien.

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.