BIZTRAC BETA
Hairdressing and barber activities

ID FRISØR AS

Org. no. 921326289 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 934,000
Operating profit NOK 65,000
Equity NOK −71,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−71k kr).

ID FRISØR AS is registered as a limited company in Trondheim, Trøndelag with organisation number 921326289. 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 30000 shares. The company's stated purpose is: “Forlag som skal tilby frisørsalong med skjønnhetspleie, samt salg av varer som tilhører bransjen.”. The most recent filed accounts, for the 2024 financial year, show NOK 934,000 in revenue and NOK 65,000 in operating profit.

Key figures · 2024

Revenue
NOK 934,000
Operating profit
NOK 65,000
Equity
NOK −71,000
Est. value
NOK 486,000

Financial health · 2024

Liquidity
0.71
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-40.1%
Weak
Equity as a share of total capital

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

Who owns ID FRISØR AS?

HOANG KRISTINE NHU NGUYEN
ID FRISØR AS
NOK 934,000 rev. · NOK 65,000 profit

ID FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ID FRISØR AS

Who owns ID FRISØR AS?

HOANG KRISTINE NHU NGUYEN is the largest registered owner, with 100.0%.

What is the revenue of ID FRISØR AS?

ID FRISØR AS had revenue of NOK 934,000 in 2024.

Who is the general manager of ID FRISØR AS?

Hoang Kristine Nhu Nguyen is registered as general manager of ID FRISØR AS.

Where is ID FRISØR AS based?

ID FRISØR AS has its business address in Trondheim.

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.