BIZTRAC BETA
Hairdressing and barber activities

ORKIDE ANDERSEN FRISØR AS

Org. no. 914819091 Limited company (AS) Ålesund Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 48,000
Equity NOK 225,000
Incorporated 2014
Share capital NOK 30,000

ORKIDE ANDERSEN FRISØR AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 914819091. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av frisørsalonger, samt hva hermed naturlig står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 48,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 48,000
Equity
NOK 225,000
Est. value
NOK 240,000

Financial health · 2024

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

Who owns ORKIDE ANDERSEN FRISØR AS?

THORLEIF ANDERSEN
ORKIDE ANDERSEN FRISØR AS
NOK 2.1m rev. · NOK 48,000 profit

ORKIDE ANDERSEN FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ORKIDE ANDERSEN FRISØR AS

Who owns ORKIDE ANDERSEN FRISØR AS?

THORLEIF ANDERSEN is the largest registered owner, with 100.0%.

What is the revenue of ORKIDE ANDERSEN FRISØR AS?

ORKIDE ANDERSEN FRISØR AS had revenue of NOK 2.1m in 2024.

Who is the general manager of ORKIDE ANDERSEN FRISØR AS?

Thorleif Andersen is registered as general manager of ORKIDE ANDERSEN FRISØR AS.

Where is ORKIDE ANDERSEN FRISØR AS based?

ORKIDE ANDERSEN FRISØR AS has its business address in Ålesund.

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.