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

STORVIK SALONG AS

Org. no. 979942397 Limited company (AS) Bodø Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK −32,000
Equity NOK 222,000
Incorporated 1998
Share capital NOK 100,000

Signals

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

STORVIK SALONG AS is registered as a limited company in Bodø, Nordland with organisation number 979942397. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 1998. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Frisørsalong og dertil hørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −32,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
▼ −7 %
Operating profit
NOK −32,000
▼ −1384 %
Equity
NOK 222,000
▼ −13 %
Est. value
NOK 957,000

Financial health · 2025

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

Who owns STORVIK SALONG AS?

STORVIK SALONG AS
NOK 1.2m rev. · NOK −32,000 profit

STORVIK SALONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORVIK SALONG AS

Who owns STORVIK SALONG AS?

Aud Schjødt Fredriksen is the largest registered owner, with 100.0%.

What is the revenue of STORVIK SALONG AS?

STORVIK SALONG AS had revenue of NOK 1.2m in 2025.

Who is the general manager of STORVIK SALONG AS?

Aud Schjødt Fredriksen is registered as general manager of STORVIK SALONG AS.

Where is STORVIK SALONG AS based?

STORVIK SALONG AS has its business address in Bodø.

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.