BIZTRAC BETA
Computer programming activities

SPOND AS

Org. no. 998209218 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 117.5m
Operating profit NOK −17.6m
Equity NOK 39.0m
Incorporated 2012
Employees 50
Share capital NOK 3.3m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−17,6 mill kr).
  • Nylig endring 2026-07-03 Aksjekapital registrert 2026-07-03.

SPOND AS is registered as a limited company in Oslo, Oslo with organisation number 998209218. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2012 and has 50 registered employees. Registered share capital is NOK 3.3m, divided into 3302258 shares. The company's stated purpose is: “Utvikle, drifte og erverve programvare og tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 117.5m in revenue and NOK −17.6m in operating profit.

Key figures · 2024

Revenue
NOK 117.5m
Operating profit
NOK −17.6m
Equity
NOK 39.0m
Est. value
NOK 201.9m

Financial health · 2024

Liquidity
1.62
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.5%
Good
Equity as a share of total capital

Who owns SPOND AS?

VERDANE IDUN D AB
SPOND AS
NOK 117.5m rev. · NOK −17.6m profit

SPOND AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does SPOND AS own?

SPOND AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SPOND AS

Who owns SPOND AS?

VERDANE IDUN D AB is the largest registered owner, with 21.7%.

What is the revenue of SPOND AS?

SPOND AS had revenue of NOK 117.5m in 2024.

Who is the general manager of SPOND AS?

Kristoffer Gallefoss is registered as general manager of SPOND AS.

Where is SPOND AS based?

SPOND 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.