BIZTRAC BETA
Retail sale of sports equipment

RIDE ON BIKE AS

Org. no. 834742802 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK 230,000
Equity NOK 95,000
Incorporated 2024
Employees 7
Share capital NOK 40,000

RIDE ON BIKE AS is registered as a limited company in Bærum, Akershus with organisation number 834742802. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2024 and has 7 registered employees. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Drive handel med sykler og sykkelutstyr, reparasjon og vedlikehold av sykler, konsulentvirksomhet, promotering samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.3m in revenue and NOK 230,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.3m
Operating profit
NOK 230,000
Equity
NOK 95,000
Est. value
NOK 654,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RIDE ON BIKE AS?

RIDE ON BIKE HOLDING AS
RIDE ON BIKE AS
NOK 4.3m rev. · NOK 230,000 profit

RIDE ON BIKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RIDE ON BIKE AS

Who owns RIDE ON BIKE AS?

RIDE ON BIKE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RIDE ON BIKE AS?

RIDE ON BIKE AS had revenue of NOK 4.3m in 2025.

Who is the general manager of RIDE ON BIKE AS?

Rajeev Rai is registered as general manager of RIDE ON BIKE AS.

Where is RIDE ON BIKE AS based?

RIDE ON BIKE AS has its business address in Høvik.

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.