BIZTRAC BETA
Uoppgitt

SPOTLIO AS

Org. no. 916539754 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK −7.2m
Equity NOK 58.5m
Incorporated 2016
Share capital NOK 4.1m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7,2 mill kr).

SPOTLIO AS is registered as a limited company in Oslo, Oslo with organisation number 916539754. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2016. Registered share capital is NOK 4.1m, divided into 203140213 shares. The company's stated purpose is: “Investering i verdipapirer og andre eiendeler, inkludert deltakelse i andre selskaper med aktiviteter knyttet til digitalisering av økosystemet rundt ski.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK −7.2m in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK −7.2m
Equity
NOK 58.5m
Est. value
NOK 32.9m

Financial health · 2025

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

Who owns SPOTLIO AS?

INVERSIS/ KESSE INV
SPOTLIO AS
NOK 3.1m rev. · NOK −7.2m profit

SPOTLIO AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does SPOTLIO AS own?

SPOTLIO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SPOTLIO AS

Who owns SPOTLIO AS?

INVERSIS/ KESSE INV is the largest registered owner, with 37.3%.

What is the revenue of SPOTLIO AS?

SPOTLIO AS had revenue of NOK 3.1m in 2025.

Who is the general manager of SPOTLIO AS?

Christian Carroll Erlandson is registered as general manager of SPOTLIO AS.

Where is SPOTLIO AS based?

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