BIZTRAC BETA
Plumbing installation

S OLSEN HOLDING AS

Org. no. 932200058 Limited company (AS) Øystre Slidre Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −348,000
Equity NOK 27.6m
Incorporated 2023
Share capital NOK 45,000

Signals

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

S OLSEN HOLDING AS is registered as a limited company in Øystre Slidre, Innlandet with organisation number 932200058. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2023. Registered share capital is NOK 45,000, divided into 150 shares. The company's stated purpose is: “Investeringer i-, drift og utleie av fast eiendom, finansielle investeringer, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −348,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −348,000
Equity
NOK 27.6m
Est. value
NOK 125.8m

Financial health · 2024

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

Who owns S OLSEN HOLDING AS?

VIDAR OLSEN HOLDING AS
S OLSEN HOLDING AS
NOK 0 rev. · NOK −348,000 profit

S OLSEN HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does S OLSEN HOLDING AS own?

S OLSEN HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about S OLSEN HOLDING AS

Who owns S OLSEN HOLDING AS?

VIDAR OLSEN HOLDING AS is the largest registered owner, with 25.3%.

What is the revenue of S OLSEN HOLDING AS?

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

Where is S OLSEN HOLDING AS based?

S OLSEN HOLDING AS has its business address in Beitostølen.

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.