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

KVALA FRISØRTEAM AS

Org. no. 918323236 Limited company (AS) Haugesund Incorporated 2016 Active
Revenue 2025 NOK 4.9m
Operating profit NOK 239,000
Equity NOK 2.2m
Incorporated 2016
Employees 7
Share capital NOK 100,000

KVALA FRISØRTEAM AS is registered as a limited company in Haugesund, Rogaland with organisation number 918323236. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2016 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Frisør og andre produkter/tjenester som naturlig hører samme med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.9m in revenue and NOK 239,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.9m
▲ +9 %
Operating profit
NOK 239,000
▼ −55 %
Equity
NOK 2.2m
▲ +10 %
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
3.62
Very good
Current assets ÷ current liabilities
Profitability
8.5%
Satisfactory
Return on total assets
Solidity
72.4%
Very good
Equity as a share of total capital

Who owns KVALA FRISØRTEAM AS?

KVALA FRISØRTEAM AS
NOK 4.9m rev. · NOK 239,000 profit

KVALA FRISØRTEAM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KVALA FRISØRTEAM AS

Who owns KVALA FRISØRTEAM AS?

Lene Thormodsen Stokvik is the largest registered owner, with 50.0%.

What is the revenue of KVALA FRISØRTEAM AS?

KVALA FRISØRTEAM AS had revenue of NOK 4.9m in 2025.

Who is the general manager of KVALA FRISØRTEAM AS?

Ingvild Rolness Nygård is registered as general manager of KVALA FRISØRTEAM AS.

Where is KVALA FRISØRTEAM AS based?

KVALA FRISØRTEAM AS has its business address in Haugesund.

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.