BIZTRAC BETA
Hairdressing and barber activities

DYRØY FRISØR AS

Org. no. 925854026 Limited company (AS) Dyrøy Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 746,000
Operating profit NOK −61,000
Equity NOK 29,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

DYRØY FRISØR AS is registered as a limited company in Dyrøy, Troms with organisation number 925854026. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av frisørsalong, samt annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 746,000 in revenue and NOK −61,000 in operating profit.

Key figures · 2025

Revenue
NOK 746,000
Operating profit
NOK −61,000
Equity
NOK 29,000
Est. value
NOK 535,000

Financial health · 2025

Liquidity
2.89
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.7%
Weak
Equity as a share of total capital

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

Who owns DYRØY FRISØR AS?

CONNIE BARDOSEN HANSSEN
DYRØY FRISØR AS
NOK 746,000 rev. · NOK −61,000 profit

DYRØY FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DYRØY FRISØR AS

Who owns DYRØY FRISØR AS?

CONNIE BARDOSEN HANSSEN is the largest registered owner, with 100.0%.

What is the revenue of DYRØY FRISØR AS?

DYRØY FRISØR AS had revenue of NOK 746,000 in 2025.

Who is the general manager of DYRØY FRISØR AS?

Connie Bardosen Hanssen is registered as general manager of DYRØY FRISØR AS.

Where is DYRØY FRISØR AS based?

DYRØY FRISØR AS has its business address in Brøstadbotn.

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.