BIZTRAC BETA
Retail sale of sports equipment

SYKKELKOMPONENTER AS

Org. no. 930983160 Limited company (AS) Bjørnafjorden Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 102.6m
Operating profit NOK 8.2m
Equity NOK 13.7m
Incorporated 2023
Employees 30
Share capital NOK 1.2m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SYKKELKOMPONENTER AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 930983160. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2023 and has 30 registered employees. Registered share capital is NOK 1.2m, divided into 100 shares. The company's stated purpose is: “Internetthandel med sykler og sykkelkomponenter, samt aktiviteter som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 102.6m in revenue and NOK 8.2m in operating profit.

Key figures · 2025

Revenue
NOK 102.6m
Operating profit
NOK 8.2m
Equity
NOK 13.7m
Est. value
NOK 36.9m

Financial health · 2025

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

Who owns SYKKELKOMPONENTER AS?

NORDTVEITGRUPPEN HOLDING AS
SYKKELKOMPONENTER AS
NOK 102.6m rev. · NOK 8.2m profit

SYKKELKOMPONENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYKKELKOMPONENTER AS

Who owns SYKKELKOMPONENTER AS?

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

What is the revenue of SYKKELKOMPONENTER AS?

SYKKELKOMPONENTER AS had revenue of NOK 102.6m in 2025.

Where is SYKKELKOMPONENTER AS based?

SYKKELKOMPONENTER AS has its business address in Baldersheim.

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.