biztrac. BETA
COMPANY REGISTER PROFILE
922797579 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Sports activities n.e.c.

EIKING VELO AS

Org. no. 922797579 Limited company (AS) Bergen Incorporated 2019 Active
Revenue 2025 NOK 0
Operating profit NOK −207,000
Equity NOK 60,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−207k kr).

EIKING VELO AS is registered as a limited company in Bergen, Vestland with organisation number 922797579. The business is classified under sports activities n.e.c. (NACE 93.190). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 3 shares. The company's stated purpose is: “Er å fremme sykkelsport og drive med investeringer relatert til sykkelsport.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −207,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −207,000
▲ +57 %
Equity
NOK 60,000
▼ −77 %
Est. value
NOK 75,000

Financial health · 2025

Liquidity
3.61
Very good
Current assets ÷ current liabilities
Profitability
-117.5%
Not satisfactory
Return on total assets
Solidity
86.0%
Weak
Equity as a share of total capital

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

Who owns EIKING VELO AS?

EIKING VELO AS
NOK 0 rev. · NOK −207,000 profit

EIKING VELO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIKING VELO AS

Who owns EIKING VELO AS?

Odd Christian Eiking is the largest registered owner, with 100.0%.

What is the revenue of EIKING VELO AS?

EIKING VELO AS had revenue of NOK 0 in 2025.

Who is the general manager of EIKING VELO AS?

Odd Christian Eiking is registered as general manager of EIKING VELO AS.

Where is EIKING VELO AS based?

EIKING VELO AS has its business address in Nesttun.

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.