BIZTRAC BETA
Hairdressing and barber activities

APPEAL FRISØR HANA AS

Org. no. 926398954 Limited company (AS) Sandnes Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 7.5m
Operating profit NOK 1.7m
Equity NOK 1.1m
Incorporated 2020
Employees 19
Share capital NOK 85,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

APPEAL FRISØR HANA AS is registered as a limited company in Sandnes, Rogaland with organisation number 926398954. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2020 and has 19 registered employees. Registered share capital is NOK 85,000, divided into 170 shares. The company's stated purpose is: “Frisørvirksomhet og hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.5m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 7.5m
Operating profit
NOK 1.7m
Equity
NOK 1.1m
Est. value
NOK 5.7m

Financial health · 2024

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

Who owns APPEAL FRISØR HANA AS?

FALCH HOLDING AS
APPEAL FRISØR HANA AS
NOK 7.5m rev. · NOK 1.7m profit

APPEAL FRISØR HANA AS has 1 registered shareholder:

All shareholders and roles →

Group structure

APPEAL FRISØR HANA AS er morselskap for 2 datterselskaper:

Frequently asked questions about APPEAL FRISØR HANA AS

Who owns APPEAL FRISØR HANA AS?

FALCH HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of APPEAL FRISØR HANA AS?

APPEAL FRISØR HANA AS had revenue of NOK 7.5m in 2024.

Where is APPEAL FRISØR HANA AS based?

APPEAL FRISØR HANA AS has its business address in Sandnes.

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.