BIZTRAC BETA
Retail sale of sports equipment

SPORT 1 KONGSBERG AS

Org. no. 879900042 Limited company (AS) Kongsberg Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 14.0m
Operating profit NOK −119,000
Equity NOK 471,000
Incorporated 1998
Employees 13
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−119k kr).

SPORT 1 KONGSBERG AS is registered as a limited company in Kongsberg, Buskerud with organisation number 879900042. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 1998 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel om import, samt deltagelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.0m in revenue and NOK −119,000 in operating profit.

Key figures · 2024

Revenue
NOK 14.0m
Operating profit
NOK −119,000
Equity
NOK 471,000
Est. value
NOK 4.8m

Financial health · 2024

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.8%
Weak
Equity as a share of total capital

Who owns SPORT 1 KONGSBERG AS?

BRONN HOLDING AS
SPORT 1 KONGSBERG AS
NOK 14.0m rev. · NOK −119,000 profit

SPORT 1 KONGSBERG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPORT 1 KONGSBERG AS

Who owns SPORT 1 KONGSBERG AS?

BRONN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SPORT 1 KONGSBERG AS?

SPORT 1 KONGSBERG AS had revenue of NOK 14.0m in 2024.

Who is the general manager of SPORT 1 KONGSBERG AS?

Rune Bronn Sandberg is registered as general manager of SPORT 1 KONGSBERG AS.

Where is SPORT 1 KONGSBERG AS based?

SPORT 1 KONGSBERG AS has its business address in Kongsberg.

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.