BIZTRAC BETA
Retail sale of sports equipment

ELSPARKVERDEN AS

Org. no. 830744452 Limited company (AS) Kristiansand Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 281,000
Operating profit NOK −3,000
Equity NOK 38,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).
  • Nylig endring 2026-07-24 Adresseendring registrert 2026-07-24.

ELSPARKVERDEN AS is registered as a limited company in Kristiansand, Agder with organisation number 830744452. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Elsparkesykkel reservedeler”. The most recent filed accounts, for the 2024 financial year, show NOK 281,000 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 281,000
Operating profit
NOK −3,000
Equity
NOK 38,000
Est. value
NOK 109,000

Financial health · 2024

Liquidity
-2.42
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
122.7%
Weak
Equity as a share of total capital

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

Who owns ELSPARKVERDEN AS?

LAREN ARELSEN
ELSPARKVERDEN AS
NOK 281,000 rev. · NOK −3,000 profit

ELSPARKVERDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELSPARKVERDEN AS

Who owns ELSPARKVERDEN AS?

LAREN ARELSEN is the largest registered owner, with 100.0%.

What is the revenue of ELSPARKVERDEN AS?

ELSPARKVERDEN AS had revenue of NOK 281,000 in 2024.

Who is the general manager of ELSPARKVERDEN AS?

Adam Arelsen is registered as general manager of ELSPARKVERDEN AS.

Where is ELSPARKVERDEN AS based?

ELSPARKVERDEN 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 15.06.2026.

Report a problem

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