BIZTRAC BETA
Retail sale of sports equipment

GAARDER SYKKELSPORT AS

Org. no. 945557583 Limited company (AS) Fredrikstad Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 8.3m
Operating profit NOK 156,000
Equity NOK 2.7m
Incorporated 1987
Employees 5
Share capital NOK 100,000

GAARDER SYKKELSPORT AS is registered as a limited company in Fredrikstad, Østfold with organisation number 945557583. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 1987 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av varer. Import og eksport, deltakelse i andre selskaper, samt kjøp og salg av eiendommer.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.3m in revenue and NOK 156,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.3m
Operating profit
NOK 156,000
Equity
NOK 2.7m
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns GAARDER SYKKELSPORT AS?

ATLE JOHANSEN HOLDING AS
GAARDER SYKKELSPORT AS
NOK 8.3m rev. · NOK 156,000 profit

GAARDER SYKKELSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GAARDER SYKKELSPORT AS

Who owns GAARDER SYKKELSPORT AS?

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

What is the revenue of GAARDER SYKKELSPORT AS?

GAARDER SYKKELSPORT AS had revenue of NOK 8.3m in 2024.

Who is the general manager of GAARDER SYKKELSPORT AS?

Atle Johansen is registered as general manager of GAARDER SYKKELSPORT AS.

Where is GAARDER SYKKELSPORT AS based?

GAARDER SYKKELSPORT AS has its business address in Fredrikstad.

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.