BIZTRAC BETA
Hairdressing and barber activities

SALONG DUETT AS

Org. no. 997894529 Limited company (AS) Ullensaker Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 694,000
Operating profit NOK 70,000
Equity NOK 73,000
Incorporated 2012
Share capital NOK 30,000

SALONG DUETT AS is registered as a limited company in Ullensaker, Akershus with organisation number 997894529. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Frisørsalong, kjøp og salg av hårpleie- og skjønnhetspleieprodukter, andre relaterte tjenester og produkter, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 694,000 in revenue and NOK 70,000 in operating profit.

Key figures · 2025

Revenue
NOK 694,000
Operating profit
NOK 70,000
Equity
NOK 73,000
Est. value
NOK 303,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SALONG DUETT AS?

ELLEN WIBEKE NILSSEN VANDVIK
SALONG DUETT AS
NOK 694,000 rev. · NOK 70,000 profit

SALONG DUETT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SALONG DUETT AS

Who owns SALONG DUETT AS?

ELLEN WIBEKE NILSSEN VANDVIK is the largest registered owner, with 100.0%.

What is the revenue of SALONG DUETT AS?

SALONG DUETT AS had revenue of NOK 694,000 in 2025.

Who is the general manager of SALONG DUETT AS?

Ellen Wibeke Nilssen Vandvik is registered as general manager of SALONG DUETT AS.

Where is SALONG DUETT AS based?

SALONG DUETT AS has its business address in Jessheim.

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.