biztrac. BETA
COMPANY REGISTER PROFILE
962108296 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Hairdressing and barber activities

RANITA FRISØRSALONGER AS

Org. no. 962108296 Limited company (AS) Øygarden Incorporated 1991 Active
Revenue 2025 NOK 0
Operating profit NOK −35,000
Equity NOK 8.2m
Incorporated 1991
Share capital NOK 1.0m

Signals

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

RANITA FRISØRSALONGER AS is registered as a limited company in Øygarden, Vestland with organisation number 962108296. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 1991. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Forvalte eierandeler i andre selskaper, blandt annet en frisørsalong, og foreta investeringer i aksjer, obligasjoner og andre verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −35,000
▲ +1 %
Equity
NOK 8.2m
▼ −1 %
Est. value
NOK 5.5m

Financial health · 2025

Liquidity
47.31
Very good
Current assets ÷ current liabilities
Profitability
3.2%
Weak
Return on total assets
Solidity
98.8%
Very good
Equity as a share of total capital

Who owns RANITA FRISØRSALONGER AS?

RANITA FRISØRSALONGER AS
NOK 0 rev. · NOK −35,000 profit

RANITA FRISØRSALONGER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RANITA FRISØRSALONGER AS

Who owns RANITA FRISØRSALONGER AS?

Alfhild Sævareid is the largest registered owner, with 100.0%.

What is the revenue of RANITA FRISØRSALONGER AS?

RANITA FRISØRSALONGER AS had revenue of NOK 0 in 2025.

Where is RANITA FRISØRSALONGER AS based?

RANITA FRISØRSALONGER AS has its business address in Straume.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.