BIZTRAC BETA
Wholesale of other household goods

PROBIKE AS

Org. no. 915686931 Limited company (AS) Bærum Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK −221,000
Equity NOK 2.3m
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−221k kr).

PROBIKE AS is registered as a limited company in Bærum, Akershus with organisation number 915686931. The business is classified under wholesale of other household goods (NACE 46.490). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å drive salg av sykler, sykkel- og sports-/friluftsutstyr, samt tilhørende virksomhet. Selskapet skal kunne delta i andre selskaper gjennom å erverve aksjer eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK −221,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK −221,000
Equity
NOK 2.3m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns PROBIKE AS?

ANDRÉ PASCAL ROSLIN
PROBIKE AS
NOK 1.7m rev. · NOK −221,000 profit

PROBIKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROBIKE AS

Who owns PROBIKE AS?

ANDRÉ PASCAL ROSLIN is the largest registered owner, with 100.0%.

What is the revenue of PROBIKE AS?

PROBIKE AS had revenue of NOK 1.7m in 2024.

Who is the general manager of PROBIKE AS?

André Pascal Roslin is registered as general manager of PROBIKE AS.

Where is PROBIKE AS based?

PROBIKE AS has its business address in Sandvika.

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.