BIZTRAC BETA
Beauty care and other beauty treatment activities

STUDIO L SANDEFJORD AS

Org. no. 822121012 Limited company (AS) Sandefjord Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 4.2m
Operating profit NOK 113,000
Equity NOK 175,000
Incorporated 2018
Employees 5
Share capital NOK 30,000

STUDIO L SANDEFJORD AS is registered as a limited company in Sandefjord, Vestfold with organisation number 822121012. The business is classified under beauty care and other beauty treatment activities (NACE 96.220). The company was incorporated in 2018 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 300000 shares. The company's stated purpose is: “Tilby hudpleie, vipper og bryn behandlinger. Negler. Fotpleie. Kurs.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK 113,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
Operating profit
NOK 113,000
Equity
NOK 175,000
Est. value
NOK 467,000

Financial health · 2025

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.7%
Satisfactory
Equity as a share of total capital

Who owns STUDIO L SANDEFJORD AS?

ROSE GULL AS
STUDIO L SANDEFJORD AS
NOK 4.2m rev. · NOK 113,000 profit

STUDIO L SANDEFJORD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STUDIO L SANDEFJORD AS

Who owns STUDIO L SANDEFJORD AS?

ROSE GULL AS is the largest registered owner, with 100.0%.

What is the revenue of STUDIO L SANDEFJORD AS?

STUDIO L SANDEFJORD AS had revenue of NOK 4.2m in 2025.

Who is the general manager of STUDIO L SANDEFJORD AS?

Albulena Berisha-Baumann is registered as general manager of STUDIO L SANDEFJORD AS.

Where is STUDIO L SANDEFJORD AS based?

STUDIO L SANDEFJORD AS has its business address in Sandefjord.

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.