BIZTRAC BETA
Landscape service activities

STIAN OLSEN HOLDING AS

Org. no. 928615928 Limited company (AS) Alta Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −43,000
Equity NOK 8.1m
Incorporated 2022
Share capital NOK 60,000

Signals

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

STIAN OLSEN HOLDING AS is registered as a limited company in Alta, Finnmark with organisation number 928615928. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2022. Registered share capital is NOK 60,000, divided into 30 shares. The company's stated purpose is: “Kjøp, besittelse og salg av aksjer i andre selskaper samt andre verdipapirer og annen virksomhet som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −43,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −43,000
Equity
NOK 8.1m
Est. value
NOK 52.0m

Financial health · 2024

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

Who owns STIAN OLSEN HOLDING AS?

STIAN OLSEN
STIAN OLSEN HOLDING AS
NOK 0 rev. · NOK −43,000 profit

STIAN OLSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STIAN OLSEN HOLDING AS own?

STIAN OLSEN HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about STIAN OLSEN HOLDING AS

Who owns STIAN OLSEN HOLDING AS?

STIAN OLSEN is the largest registered owner, with 100.0%.

What is the revenue of STIAN OLSEN HOLDING AS?

STIAN OLSEN HOLDING AS had revenue of NOK 0 in 2024.

Where is STIAN OLSEN HOLDING AS based?

STIAN OLSEN HOLDING AS has its business address in Alta.

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.