BIZTRAC BETA
Hairdressing and barber activities

HAIR I KROSSEN AS

Org. no. 925591238 Limited company (AS) Karmøy Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 420,000
Equity NOK 1.2m
Incorporated 2020
Employees 5
Share capital NOK 100,000

HAIR I KROSSEN AS is registered as a limited company in Karmøy, Rogaland with organisation number 925591238. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2020 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive frisørsalong, annen skjønnhetspleie, handel samt hva herved står i forbindelse, herunder deltakelse i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 420,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK 420,000
Equity
NOK 1.2m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns HAIR I KROSSEN AS?

GUDRUN SYNNØVE LANGÅKER ADELSTEN
HAIR I KROSSEN AS
NOK 3.7m rev. · NOK 420,000 profit

HAIR I KROSSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAIR I KROSSEN AS

Who owns HAIR I KROSSEN AS?

GUDRUN SYNNØVE LANGÅKER ADELSTEN is the largest registered owner, with 100.0%.

What is the revenue of HAIR I KROSSEN AS?

HAIR I KROSSEN AS had revenue of NOK 3.7m in 2025.

Who is the general manager of HAIR I KROSSEN AS?

Gudrun Synnøve Langåker Adelsten is registered as general manager of HAIR I KROSSEN AS.

Where is HAIR I KROSSEN AS based?

HAIR I KROSSEN AS has its business address in Åkrehamn.

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.