BIZTRAC BETA
Hairdressing and barber activities

ANKAS FRISØR AS

Org. no. 927834820 Limited company (AS) Hammerfest Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK −20,000
Equity NOK 125,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

ANKAS FRISØR AS is registered as a limited company in Hammerfest, Finnmark with organisation number 927834820. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Klipp og frisering av hår, kjøp og salg av hår og skjønnhetsprodukter, konsulent tjenester innen frisørfaget og annet som naturlig hører inn under foranstående.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK −20,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK −20,000
Equity
NOK 125,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns ANKAS FRISØR AS?

ANN KRISTIN SEBERGSEN
ANKAS FRISØR AS
NOK 1.4m rev. · NOK −20,000 profit

ANKAS FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ANKAS FRISØR AS

Who owns ANKAS FRISØR AS?

ANN KRISTIN SEBERGSEN is the largest registered owner, with 100.0%.

What is the revenue of ANKAS FRISØR AS?

ANKAS FRISØR AS had revenue of NOK 1.4m in 2025.

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

Ann Kristin Sebergsen is registered as general manager of ANKAS FRISØR AS.

Where is ANKAS FRISØR AS based?

ANKAS FRISØR AS has its business address in Hammerfest.

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.