BIZTRAC BETA
Hairdressing and barber activities

FROGNER HÅRSTUDIO AS

Org. no. 926562436 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 6,000
Equity NOK 90,000
Incorporated 2021
Share capital NOK 30,000

FROGNER HÅRSTUDIO AS is registered as a limited company in Oslo, Oslo with organisation number 926562436. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Frisør- og velværetjenester for damer og herrer, samt alt som dertil hører til. Selskapet kan også investere i verdipapirer og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 6,000
Equity
NOK 90,000
Est. value
NOK 61,000

Financial health · 2025

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

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

Who owns FROGNER HÅRSTUDIO AS?

TOVE BROVOLD AANESRUD
FROGNER HÅRSTUDIO AS
NOK 1.3m rev. · NOK 6,000 profit

FROGNER HÅRSTUDIO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FROGNER HÅRSTUDIO AS

Who owns FROGNER HÅRSTUDIO AS?

TOVE BROVOLD AANESRUD is the largest registered owner, with 100.0%.

What is the revenue of FROGNER HÅRSTUDIO AS?

FROGNER HÅRSTUDIO AS had revenue of NOK 1.3m in 2025.

Who is the general manager of FROGNER HÅRSTUDIO AS?

Tove Brovold Aanesrud is registered as general manager of FROGNER HÅRSTUDIO AS.

Where is FROGNER HÅRSTUDIO AS based?

FROGNER HÅRSTUDIO AS has its business address in Oslo.

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.