BIZTRAC BETA
Hairdressing and barber activities

FRICO AS

Org. no. 950919914 Limited company (AS) Stavanger Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 179,000
Operating profit NOK −1.0m
Equity NOK 194,000
Incorporated 1988
Share capital NOK 182,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,0 mill kr).

FRICO AS is registered as a limited company in Stavanger, Rogaland with organisation number 950919914. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 1988. Registered share capital is NOK 182,000, divided into 182 shares. The company's stated purpose is: “Handel, tjenesteyting og investeringer samt hva hermed står i forbindelse, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 179,000 in revenue and NOK −1.0m in operating profit.

Key figures · 2024

Revenue
NOK 179,000
Operating profit
NOK −1.0m
Equity
NOK 194,000
Est. value
NOK 222,000

Financial health · 2024

Liquidity
0.28
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.2%
Weak
Equity as a share of total capital

Who owns FRICO AS?

SNORRE R HOLDING AS
FRICO AS
NOK 179,000 rev. · NOK −1.0m profit

FRICO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FRICO AS own?

FRICO AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about FRICO AS

Who owns FRICO AS?

SNORRE R HOLDING AS is the largest registered owner, with 97.8%.

What is the revenue of FRICO AS?

FRICO AS had revenue of NOK 179,000 in 2024.

Who is the general manager of FRICO AS?

Snorre Risa is registered as general manager of FRICO AS.

Where is FRICO AS based?

FRICO AS has its business address in Stavanger.

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.