BIZTRAC BETA
Retail sale of sports equipment

I-SPORT ROSEBY AS

Org. no. 957779085 Limited company (AS) Molde Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 28.8m
Operating profit NOK 1.3m
Equity NOK 5.4m
Incorporated 1990
Employees 29
Share capital NOK 850,000

I-SPORT ROSEBY AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 957779085. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 1990 and has 29 registered employees. Registered share capital is NOK 850,000. The company's stated purpose is: “Butikkhandel innen sports- og fritidsbransjen, detaljhandel innen tekstil og annet som står i forbindelse hermed, herunder aksjetegning og deltakelse i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.8m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 28.8m
Operating profit
NOK 1.3m
Equity
NOK 5.4m
Est. value
NOK 7.6m

Financial health · 2024

Liquidity
1.62
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.5%
Good
Equity as a share of total capital

Who owns I-SPORT ROSEBY AS?

3S HOLDING AS
I-SPORT ROSEBY AS
NOK 28.8m rev. · NOK 1.3m profit

I-SPORT ROSEBY AS has 1 registered shareholder:

All shareholders and roles →

Group structure

I-SPORT ROSEBY AS er morselskap for 5 datterselskaper:

Frequently asked questions about I-SPORT ROSEBY AS

Who owns I-SPORT ROSEBY AS?

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

What is the revenue of I-SPORT ROSEBY AS?

I-SPORT ROSEBY AS had revenue of NOK 28.8m in 2024.

Who is the general manager of I-SPORT ROSEBY AS?

Jan Åge Wiik is registered as general manager of I-SPORT ROSEBY AS.

Where is I-SPORT ROSEBY AS based?

I-SPORT ROSEBY AS has its business address in Molde.

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.