BIZTRAC BETA
Hairdressing and barber activities

ENVY HÅRSTUDIO AS

Org. no. 913492153 Limited company (AS) Sola Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −23,000
Equity NOK 505,000
Incorporated 2014
Share capital NOK 55,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−23k kr).

ENVY HÅRSTUDIO AS is registered as a limited company in Sola, Rogaland with organisation number 913492153. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2014. Registered share capital is NOK 55,000, divided into 55469 shares. The company's stated purpose is: “Frisørvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −23,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −23,000
Equity
NOK 505,000
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
1.10
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
46.0%
Very good
Equity as a share of total capital

Who owns ENVY HÅRSTUDIO AS?

KINE KOPPANG
ENVY HÅRSTUDIO AS
NOK 2.1m rev. · NOK −23,000 profit

ENVY HÅRSTUDIO AS has 4 registered shareholders:

All shareholders and roles →

Which companies does ENVY HÅRSTUDIO AS own?

ENVY HÅRSTUDIO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ENVY HÅRSTUDIO AS

Who owns ENVY HÅRSTUDIO AS?

KINE KOPPANG is the largest registered owner, with 45.1%.

What is the revenue of ENVY HÅRSTUDIO AS?

ENVY HÅRSTUDIO AS had revenue of NOK 2.1m in 2024.

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

Kine Koppang is registered as general manager of ENVY HÅRSTUDIO AS.

Where is ENVY HÅRSTUDIO AS based?

ENVY HÅRSTUDIO AS has its business address in Sola.

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.