BIZTRAC BETA
Computer programming activities

SPOORTZ HOLDING AS

Org. no. 920930271 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −181,000
Equity NOK 22.4m
Incorporated 2018
Share capital NOK 1.5m

Signals

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

SPOORTZ HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 920930271. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2018. Registered share capital is NOK 1.5m, divided into 15073157 shares. The company's stated purpose is: “Som investeringsselskap å forvalte sine eierinteresser i Spond AS (org nr 998 209 218), innenfor rammen av det til enhver tid gjeldende lovgivning.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −181,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −181,000
Equity
NOK 22.4m
Est. value
NOK 40.6m

Financial health · 2024

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

Who owns SPOORTZ HOLDING AS?

TUCAN HOLDING AS
SPOORTZ HOLDING AS
NOK 0 rev. · NOK −181,000 profit

SPOORTZ HOLDING AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does SPOORTZ HOLDING AS own?

SPOORTZ HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SPOORTZ HOLDING AS

Who owns SPOORTZ HOLDING AS?

TUCAN HOLDING AS is the largest registered owner, with 15.2%.

What is the revenue of SPOORTZ HOLDING AS?

SPOORTZ HOLDING AS had revenue of NOK 0 in 2024.

Where is SPOORTZ HOLDING AS based?

SPOORTZ HOLDING AS has its business address in Oslo.

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.