BIZTRAC BETA
Retail sale of sports equipment

INTERSPORT CITY SYD AS

Org. no. 930891622 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 21.7m
Operating profit NOK 577,000
Equity NOK 124,000
Incorporated 2023
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.

INTERSPORT CITY SYD AS is registered as a limited company in Trondheim, Trøndelag with organisation number 930891622. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2023 and has 12 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av sportsutstyr, samt alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.7m in revenue and NOK 577,000 in operating profit.

Key figures · 2024

Revenue
NOK 21.7m
Operating profit
NOK 577,000
Equity
NOK 124,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns INTERSPORT CITY SYD AS?

SAKSHAUG SPORT HOLDING AS
INTERSPORT CITY SYD AS
NOK 21.7m rev. · NOK 577,000 profit

INTERSPORT CITY SYD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INTERSPORT CITY SYD AS

Who owns INTERSPORT CITY SYD AS?

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

What is the revenue of INTERSPORT CITY SYD AS?

INTERSPORT CITY SYD AS had revenue of NOK 21.7m in 2024.

Where is INTERSPORT CITY SYD AS based?

INTERSPORT CITY SYD AS has its business address in Tiller.

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.