BIZTRAC BETA
Dental practice care activities

CHRYSO HOLDING AS

Org. no. 934141679 Limited company (AS) Stord Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 656,000
Operating profit NOK 481,000
Equity NOK 401,000
Incorporated 2024
Share capital NOK 30,000

CHRYSO HOLDING AS is registered as a limited company in Stord, Vestland with organisation number 934141679. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tannhelsetjenester, kjeveortopedisk behandling, investering i selskaper, verdipapirer, eiendom mm.”. The most recent filed accounts, for the 2024 financial year, show NOK 656,000 in revenue and NOK 481,000 in operating profit.

Key figures · 2024

Revenue
NOK 656,000
Operating profit
NOK 481,000
Equity
NOK 401,000
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns CHRYSO HOLDING AS?

HÅKON GULLIKSEN
CHRYSO HOLDING AS
NOK 656,000 rev. · NOK 481,000 profit

CHRYSO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CHRYSO HOLDING AS own?

CHRYSO HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CHRYSO HOLDING AS

Who owns CHRYSO HOLDING AS?

HÅKON GULLIKSEN is the largest registered owner, with 100.0%.

What is the revenue of CHRYSO HOLDING AS?

CHRYSO HOLDING AS had revenue of NOK 656,000 in 2024.

Who is the general manager of CHRYSO HOLDING AS?

Håkon Gulliksen is registered as general manager of CHRYSO HOLDING AS.

Where is CHRYSO HOLDING AS based?

CHRYSO HOLDING AS has its business address in Stord.

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.