BIZTRAC BETA
Rental and operating of own or leased real estate

SOLLID HOLDING AS

Org. no. 817039812 Limited company (AS) Volda Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK 2.3m
Incorporated 2016
Share capital NOK 75,000

Signals

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

SOLLID HOLDING AS is registered as a limited company in Volda, Møre og Romsdal with organisation number 817039812. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 75,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer og eiendom og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet har videre som formål å drive oppføring og vedlikehold av bygninger, samt hva som naturlig måtte stå i forbindelse med dette”.

Key figures · 2025

Operating profit
NOK −21,000
Equity
NOK 2.3m
Est. value
NOK 3.8m

Financial health · 2025

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

Who owns SOLLID HOLDING AS?

KNUT MARTIN ANDREAS SOLLID
SOLLID HOLDING AS
· NOK −21,000 profit

SOLLID HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SOLLID HOLDING AS own?

SOLLID HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about SOLLID HOLDING AS

Who owns SOLLID HOLDING AS?

KNUT MARTIN ANDREAS SOLLID is the largest registered owner, with 100.0%.

Where is SOLLID HOLDING AS based?

SOLLID HOLDING AS has its business address in Hornindal.

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.