BIZTRAC BETA
Retail sale of sports equipment

SPORTEN VOSS AS

Org. no. 999326455 Limited company (AS) Voss Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 25.3m
Operating profit NOK 907,000
Equity NOK 5.6m
Incorporated 2012
Employees 12
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SPORTEN VOSS AS is registered as a limited company in Voss, Vestland with organisation number 999326455. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2012 and has 12 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapets formål er drift av sportsforretning samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 25.3m in revenue and NOK 907,000 in operating profit.

Key figures · 2024

Revenue
NOK 25.3m
Operating profit
NOK 907,000
Equity
NOK 5.6m
Est. value
NOK 6.3m

Financial health · 2024

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

Who owns SPORTEN VOSS AS?

STICA INVEST AS
SPORTEN VOSS AS
NOK 25.3m rev. · NOK 907,000 profit

SPORTEN VOSS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPORTEN VOSS AS

Who owns SPORTEN VOSS AS?

STICA INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of SPORTEN VOSS AS?

SPORTEN VOSS AS had revenue of NOK 25.3m in 2024.

Who is the general manager of SPORTEN VOSS AS?

Ragnar Grønås is registered as general manager of SPORTEN VOSS AS.

Where is SPORTEN VOSS AS based?

SPORTEN VOSS AS has its business address in Voss.

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.