BIZTRAC BETA
Hairdressing and barber activities

RAGNHILD STRØM AS

Org. no. 919309881 Limited company (AS) Harstad Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 195,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

RAGNHILD STRØM AS is registered as a limited company in Harstad, Troms with organisation number 919309881. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Frisørvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 195,000
Est. value
NOK 258,000

Financial health · 2025

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

Who owns RAGNHILD STRØM AS?

RAGNHILD STRØM-WILLUMSEN
RAGNHILD STRØM AS
NOK 0 rev. · NOK −18,000 profit

RAGNHILD STRØM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RAGNHILD STRØM AS own?

RAGNHILD STRØM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RAGNHILD STRØM AS

Who owns RAGNHILD STRØM AS?

RAGNHILD STRØM-WILLUMSEN is the largest registered owner, with 100.0%.

What is the revenue of RAGNHILD STRØM AS?

RAGNHILD STRØM AS had revenue of NOK 0 in 2025.

Who is the general manager of RAGNHILD STRØM AS?

Ragnhild Strøm-Willumsen is registered as general manager of RAGNHILD STRØM AS.

Where is RAGNHILD STRØM AS based?

RAGNHILD STRØM AS has its business address in Harstad.

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.