BIZTRAC BETA
Beauty care and other beauty treatment activities

STUDIO C FAUSKE AS

Org. no. 932836637 Limited company (AS) Fauske Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 615,000
Operating profit NOK 32,000
Equity NOK 49,000
Incorporated 2023
Share capital NOK 30,000

STUDIO C FAUSKE AS is registered as a limited company in Fauske, Nordland with organisation number 932836637. The business is classified under beauty care and other beauty treatment activities (NACE 96.220). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Skjønnhetssalong - egenpleie, velværebehandlinger, vipper, bryn. Salg av kosmetikk/hudpleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 615,000 in revenue and NOK 32,000 in operating profit.

Key figures · 2025

Revenue
NOK 615,000
Operating profit
NOK 32,000
Equity
NOK 49,000
Est. value
NOK 147,000

Financial health · 2024

Liquidity
1.56
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.8%
Weak
Equity as a share of total capital

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

Who owns STUDIO C FAUSKE AS?

CECILIE VESTERVOLL PAULSEN
STUDIO C FAUSKE AS
NOK 615,000 rev. · NOK 32,000 profit

STUDIO C FAUSKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STUDIO C FAUSKE AS

Who owns STUDIO C FAUSKE AS?

CECILIE VESTERVOLL PAULSEN is the largest registered owner, with 100.0%.

What is the revenue of STUDIO C FAUSKE AS?

STUDIO C FAUSKE AS had revenue of NOK 615,000 in 2025.

Who is the general manager of STUDIO C FAUSKE AS?

Cecilie Vestervoll Paulsen is registered as general manager of STUDIO C FAUSKE AS.

Where is STUDIO C FAUSKE AS based?

STUDIO C FAUSKE AS has its business address in Valnesfjord.

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.