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

VOX SOLBERGELVA AS

Org. no. 999326242 Limited company (AS) Drammen Incorporated 2012 Active
Revenue 2025 NOK 3.2m
Operating profit NOK 196,000
Equity NOK 302,000
Incorporated 2012
Employees 8
Share capital NOK 60,000

VOX SOLBERGELVA AS is registered as a limited company in Drammen, Buskerud with organisation number 999326242. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2012 and has 8 registered employees. Registered share capital is NOK 60,000, divided into 600 shares. The company's stated purpose is: “Frisørsalong og alt som står i forbindelse med dette - herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 196,000 in operating profit.

Former names: TANGO SOLBERGELVA AS

Key figures · 2025

Revenue
NOK 3.2m
▲ +0 %
Operating profit
NOK 196,000
▼ −47 %
Equity
NOK 302,000
▼ −83 %
Est. value
NOK 973,000

Financial health · 2025

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
10.6%
Good
Return on total assets
Solidity
12.0%
Satisfactory
Equity as a share of total capital

Who owns VOX SOLBERGELVA AS?

VOX SOLBERGELVA AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about VOX SOLBERGELVA AS

Who owns VOX SOLBERGELVA AS?

Terje Stryken is the largest registered owner, with 36.0%.

What is the revenue of VOX SOLBERGELVA AS?

VOX SOLBERGELVA AS had revenue of NOK 3.2m in 2025.

Who is the general manager of VOX SOLBERGELVA AS?

Hilde Storm-Syvertsen is registered as general manager of VOX SOLBERGELVA AS.

Where is VOX SOLBERGELVA AS based?

VOX SOLBERGELVA AS has its business address in Solbergelva.

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.