BIZTRAC BETA
Hairdressing and barber activities

DOBBELVSTUDIO AS

Org. no. 933911802 Limited company (AS) Stavanger Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 26,000
Operating profit NOK 6,000
Equity NOK 12,000
Incorporated 2024
Share capital NOK 30,000

DOBBELVSTUDIO AS is registered as a limited company in Stavanger, Rogaland with organisation number 933911802. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen skjønnhetspleie - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 26,000 in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 26,000
Operating profit
NOK 6,000
Equity
NOK 12,000
Est. value
NOK 26,000

Financial health · 2025

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

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

Who owns DOBBELVSTUDIO AS?

VILDE RØRHEIM VATNALAND
DOBBELVSTUDIO AS
NOK 26,000 rev. · NOK 6,000 profit

DOBBELVSTUDIO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DOBBELVSTUDIO AS

Who owns DOBBELVSTUDIO AS?

VILDE RØRHEIM VATNALAND is the largest registered owner, with 100.0%.

What is the revenue of DOBBELVSTUDIO AS?

DOBBELVSTUDIO AS had revenue of NOK 26,000 in 2025.

Who is the general manager of DOBBELVSTUDIO AS?

Vilde Rørheim Vatnaland is registered as general manager of DOBBELVSTUDIO AS.

Where is DOBBELVSTUDIO AS based?

DOBBELVSTUDIO AS has its business address in Finnøy.

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.