BIZTRAC BETA
Hairdressing and barber activities

TWISTER HÅRDESIGN AS

Org. no. 985442533 Limited company (AS) Bergen Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK −43,000
Equity NOK 127,000
Incorporated 2003
Employees 5
Share capital NOK 100,000

Signals

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

TWISTER HÅRDESIGN AS is registered as a limited company in Bergen, Vestland with organisation number 985442533. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2003 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Frisørsalong, handel og agentur, med dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK −43,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK −43,000
Equity
NOK 127,000
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
1.40
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.4%
Good
Equity as a share of total capital

Who owns TWISTER HÅRDESIGN AS?

ANJA CECILIE HEGLAND
TWISTER HÅRDESIGN AS
NOK 2.2m rev. · NOK −43,000 profit

TWISTER HÅRDESIGN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TWISTER HÅRDESIGN AS

Who owns TWISTER HÅRDESIGN AS?

ANJA CECILIE HEGLAND is the largest registered owner, with 100.0%.

What is the revenue of TWISTER HÅRDESIGN AS?

TWISTER HÅRDESIGN AS had revenue of NOK 2.2m in 2025.

Who is the general manager of TWISTER HÅRDESIGN AS?

Anja Cecilie Hegland is registered as general manager of TWISTER HÅRDESIGN AS.

Where is TWISTER HÅRDESIGN AS based?

TWISTER HÅRDESIGN AS has its business address in Bønes.

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.