BIZTRAC BETA
Uoppgitt

OLAUSSEN SKOHOLDING AS

Org. no. 927596539 Limited company (AS) Kristiansand Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −19,000
Equity NOK 127.3m
Incorporated 2021
Share capital NOK 30,000

Signals

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

OLAUSSEN SKOHOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 927596539. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, forvaltning av detaljhandel, skofaghandel og dertil naturlig tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −19,000
Equity
NOK 127.3m
Est. value
NOK 125.2m

Financial health · 2024

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

Who owns OLAUSSEN SKOHOLDING AS?

MAGNUS OLAUSSEN
OLAUSSEN SKOHOLDING AS
NOK 0 rev. · NOK −19,000 profit

OLAUSSEN SKOHOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OLAUSSEN SKOHOLDING AS own?

OLAUSSEN SKOHOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OLAUSSEN SKOHOLDING AS

Who owns OLAUSSEN SKOHOLDING AS?

MAGNUS OLAUSSEN is the largest registered owner, with 100.0%.

What is the revenue of OLAUSSEN SKOHOLDING AS?

OLAUSSEN SKOHOLDING AS had revenue of NOK 0 in 2024.

Where is OLAUSSEN SKOHOLDING AS based?

OLAUSSEN SKOHOLDING AS has its business address in Kristiansand S.

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.