BIZTRAC BETA
Hairdressing and barber activities

FLORYA FRISØR AS

Org. no. 928538788 Limited company (AS) Sola Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 948,000
Operating profit NOK −45,000
Equity NOK 69,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

FLORYA FRISØR AS is registered as a limited company in Sola, Rogaland with organisation number 928538788. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Frisørvirksomhet, annen velværepleie og handel som står i forbindelse hermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 948,000 in revenue and NOK −45,000 in operating profit.

Key figures · 2025

Revenue
NOK 948,000
Operating profit
NOK −45,000
Equity
NOK 69,000
Est. value
NOK 696,000

Financial health · 2025

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

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

Who owns FLORYA FRISØR AS?

LINA MAMON AHMED MAHARMA
FLORYA FRISØR AS
NOK 948,000 rev. · NOK −45,000 profit

FLORYA FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLORYA FRISØR AS

Who owns FLORYA FRISØR AS?

LINA MAMON AHMED MAHARMA is the largest registered owner, with 100.0%.

What is the revenue of FLORYA FRISØR AS?

FLORYA FRISØR AS had revenue of NOK 948,000 in 2025.

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

Lina Mamon Ahmed Maharma is registered as general manager of FLORYA FRISØR AS.

Where is FLORYA FRISØR AS based?

FLORYA FRISØR AS has its business address in Sola.

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.