BIZTRAC BETA
Hairdressing and barber activities

FLOE AS

Org. no. 932116421 Limited company (AS) Hammerfest Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 7.7m
Operating profit NOK −396,000
Equity NOK 40,000
Incorporated 2023
Employees 7
Share capital NOK 40,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−396k kr).

FLOE AS is registered as a limited company in Hammerfest, Finnmark with organisation number 932116421. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2023 and has 7 registered employees. Registered share capital is NOK 40,000, divided into 1000 shares. The company's stated purpose is: “Hår og skjønnhetspleie samt salg av tilhørende produkter. Selskapet kan også delta i annen virksomhet med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.7m in revenue and NOK −396,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.7m
Operating profit
NOK −396,000
Equity
NOK 40,000
Est. value
NOK 4.6m

Financial health · 2024

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

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

Who owns FLOE AS?

MARTINE LANGSETH HOLDING AS
FLOE AS
NOK 7.7m rev. · NOK −396,000 profit

FLOE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLOE AS

Who owns FLOE AS?

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

What is the revenue of FLOE AS?

FLOE AS had revenue of NOK 7.7m in 2024.

Who is the general manager of FLOE AS?

Martine Arnesen Langseth is registered as general manager of FLOE AS.

Where is FLOE AS based?

FLOE 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.