biztrac. BETA
COMPANY REGISTER PROFILE
921772505 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Hairdressing and barber activities

KASAMA STUDIO AS

Org. no. 921772505 Limited company (AS) Bærum Incorporated 2018 Active
Revenue 2025 NOK 789,000
Operating profit NOK −828
Equity NOK 378,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−828 kr).

KASAMA STUDIO AS is registered as a limited company in Bærum, Akershus with organisation number 921772505. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Profesjonell utførelse av hårpleie og frisyredesign.”. The most recent filed accounts, for the 2025 financial year, show NOK 789,000 in revenue and NOK −828 in operating profit.

Former names: YVONNE STUDIO AS

Key figures · 2025

Revenue
NOK 789,000
▼ −5 %
Operating profit
NOK −828
▲ +44 %
Equity
NOK 378,000
▲ +0 %
Est. value
NOK 741,000

Financial health · 2025

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

Who owns KASAMA STUDIO AS?

KASAMA STUDIO AS
NOK 789,000 rev. · NOK −828 profit

KASAMA STUDIO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KASAMA STUDIO AS

Who owns KASAMA STUDIO AS?

Kasama Vestli is the largest registered owner, with 100.0%.

What is the revenue of KASAMA STUDIO AS?

KASAMA STUDIO AS had revenue of NOK 789,000 in 2025.

Who is the general manager of KASAMA STUDIO AS?

Kasama Vestli is registered as general manager of KASAMA STUDIO AS.

Where is KASAMA STUDIO AS based?

KASAMA STUDIO AS has its business address in Sandvika.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.