BIZTRAC BETA
Uoppgitt

STAVANG OLSEN HOLDING AS

Org. no. 926643878 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK 162,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

STAVANG OLSEN HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 926643878. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −14,000
Equity
NOK 162,000
Est. value
NOK 689,000

Financial health · 2025

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

Who owns STAVANG OLSEN HOLDING AS?

KIM STAVANG OLSEN
STAVANG OLSEN HOLDING AS
· NOK −14,000 profit

STAVANG OLSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STAVANG OLSEN HOLDING AS own?

STAVANG OLSEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STAVANG OLSEN HOLDING AS

Who owns STAVANG OLSEN HOLDING AS?

KIM STAVANG OLSEN is the largest registered owner, with 100.0%.

Who is the general manager of STAVANG OLSEN HOLDING AS?

Kim Stavang Olsen is registered as general manager of STAVANG OLSEN HOLDING AS.

Where is STAVANG OLSEN HOLDING AS based?

STAVANG OLSEN HOLDING AS has its business address in Garnes.

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.