biztrac. BETA
COMPANY REGISTER PROFILE
928261425 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

SPARKEL AS

Org. no. 928261425 Limited company (AS) Bærum Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK −880,000
Equity NOK 819,000
Incorporated 2021
Share capital NOK 32,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−880k kr).
  • Nylig endring 2026-04-16 Adresseendring registrert 2026-04-16.

SPARKEL AS is registered as a limited company in Bærum, Akershus with organisation number 928261425. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021. Registered share capital is NOK 32,000, divided into 2130384 shares. The company's stated purpose is: “Utvikling og salg av programvare til bygg- og anleggsbransjen og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK −880,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
▼ −24 %
Operating profit
NOK −880,000
▼ −269 %
Equity
NOK 819,000
▼ −52 %
Est. value
NOK 3.1m

Financial health · 2025

Liquidity
3.44
Very good
Current assets ÷ current liabilities
Profitability
-52.5%
Not satisfactory
Return on total assets
Solidity
71.6%
Very good
Equity as a share of total capital

Who owns SPARKEL AS?

SPARKEL AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPARKEL AS

Who owns SPARKEL AS?

ACRE AS is the largest registered owner, with 66.9%.

What is the revenue of SPARKEL AS?

SPARKEL AS had revenue of NOK 1.6m in 2025.

Who is the general manager of SPARKEL AS?

Magnus Nilsen is registered as general manager of SPARKEL AS.

Where is SPARKEL AS based?

SPARKEL AS has its business address in Fornebu.

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.