BIZTRAC BETA
Uoppgitt

SPARKY INVEST AS

Org. no. 933461971 Limited company (AS) Hemsedal Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 519,000
Incorporated 2024
Share capital NOK 300,000

Signals

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

SPARKY INVEST AS is registered as a limited company in Hemsedal, Buskerud with organisation number 933461971. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 300,000, divided into 300000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 519,000
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns SPARKY INVEST AS?

DANIEL HALBJØRHUS
SPARKY INVEST AS
NOK 0 rev. · NOK −7,000 profit

SPARKY INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SPARKY INVEST AS own?

SPARKY INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SPARKY INVEST AS

Who owns SPARKY INVEST AS?

DANIEL HALBJØRHUS is the largest registered owner, with 100.0%.

What is the revenue of SPARKY INVEST AS?

SPARKY INVEST AS had revenue of NOK 0 in 2025.

Where is SPARKY INVEST AS based?

SPARKY INVEST AS has its business address in Hemsedal.

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.