BIZTRAC BETA
Hairdressing and barber activities

SOLBYGG HOLDING AS

Org. no. 979454058 Limited company (AS) Kristiansand Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 162,000
Equity NOK 215,000
Incorporated 1997
Share capital NOK 30,000

SOLBYGG HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 979454058. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 1997. Registered share capital is NOK 30,000, divided into 300000 shares. The company's stated purpose is: “Investering i verdipapirer og eiendom, samt frisørvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 162,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 162,000
Equity
NOK 215,000
Est. value
NOK 676,000

Financial health · 2025

Liquidity
0.25
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.7%
Satisfactory
Equity as a share of total capital

Who owns SOLBYGG HOLDING AS?

CHRISTIAN GUNNUFSEN
SOLBYGG HOLDING AS
NOK 1.9m rev. · NOK 162,000 profit

SOLBYGG HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SOLBYGG HOLDING AS own?

SOLBYGG HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SOLBYGG HOLDING AS

Who owns SOLBYGG HOLDING AS?

CHRISTIAN GUNNUFSEN is the largest registered owner, with 98.5%.

What is the revenue of SOLBYGG HOLDING AS?

SOLBYGG HOLDING AS had revenue of NOK 1.9m in 2025.

Who is the general manager of SOLBYGG HOLDING AS?

Christian Gunnufsen is registered as general manager of SOLBYGG HOLDING AS.

Where is SOLBYGG HOLDING AS based?

SOLBYGG HOLDING 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.