BIZTRAC BETA
Beauty care and other beauty treatment activities

CLINIQUE CICERONE AS

Org. no. 990022542 Limited company (AS) Trondheim Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 580,000
Equity NOK 2.5m
Incorporated 2006
Share capital NOK 250,000

CLINIQUE CICERONE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 990022542. The business is classified under beauty care and other beauty treatment activities (NACE 96.220). The company was incorporated in 2006. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Handel, hud, fot og kroppspleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 580,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 580,000
Equity
NOK 2.5m
Est. value
NOK 3.5m

Financial health · 2024

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

Who owns CLINIQUE CICERONE AS?

CICERONE HOLDING AS
CLINIQUE CICERONE AS
NOK 3.8m rev. · NOK 580,000 profit

CLINIQUE CICERONE AS has 4 registered shareholders:

All shareholders and roles →

Which companies does CLINIQUE CICERONE AS own?

CLINIQUE CICERONE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CLINIQUE CICERONE AS

Who owns CLINIQUE CICERONE AS?

CICERONE HOLDING AS is the largest registered owner, with 60.0%.

What is the revenue of CLINIQUE CICERONE AS?

CLINIQUE CICERONE AS had revenue of NOK 3.8m in 2024.

Who is the general manager of CLINIQUE CICERONE AS?

Vibeke Dahl is registered as general manager of CLINIQUE CICERONE AS.

Where is CLINIQUE CICERONE AS based?

CLINIQUE CICERONE AS has its business address in Trondheim.

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.