biztrac. BETA
COMPANY REGISTER PROFILE
958134738 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of sports equipment

KRISTIANSAND SYKKELSENTER AS

Org. no. 958134738 Limited company (AS) Kristiansand Incorporated 1990 Active
Revenue 2025 NOK 15.5m
Operating profit NOK 813,000
Equity NOK 881,000
Incorporated 1990
Employees 6
Share capital NOK 1.0m

KRISTIANSAND SYKKELSENTER AS is registered as a limited company in Kristiansand, Agder with organisation number 958134738. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 1990 and has 6 registered employees. Registered share capital is NOK 1.0m, divided into 1009 shares. The company's stated purpose is: “Handel.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.5m in revenue and NOK 813,000 in operating profit.

Key figures · 2025

Revenue
NOK 15.5m
▲ +18 %
Operating profit
NOK 813,000
▲ +491 %
Equity
NOK 881,000
▲ +22 %
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
2.53
Very good
Current assets ÷ current liabilities
Profitability
8.8%
Satisfactory
Return on total assets
Solidity
10.4%
Satisfactory
Equity as a share of total capital

Who owns KRISTIANSAND SYKKELSENTER AS?

KRISTIANSAND SYKKELSENTER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KRISTIANSAND SYKKELSENTER AS

Who owns KRISTIANSAND SYKKELSENTER AS?

Svein Bergheim is the largest registered owner, with 85.6%.

What is the revenue of KRISTIANSAND SYKKELSENTER AS?

KRISTIANSAND SYKKELSENTER AS had revenue of NOK 15.5m in 2025.

Who is the general manager of KRISTIANSAND SYKKELSENTER AS?

Svein Bergheim is registered as general manager of KRISTIANSAND SYKKELSENTER AS.

Where is KRISTIANSAND SYKKELSENTER AS based?

KRISTIANSAND SYKKELSENTER AS has its business address in Kristiansand S.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.