BIZTRAC BETA
Uoppgitt

STO HOLDING AS

Org. no. 920229352 Limited company (AS) Trondheim Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −69,000
Equity NOK 2.9m
Incorporated 2017
Share capital NOK 30,000

Signals

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

STO HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 920229352. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selv, eller ved deltakelse i, eller i samarbeid med andre selskaper, å investere i aksjer, eiendom eller dertil hørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −69,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −69,000
Equity
NOK 2.9m
Est. value
NOK 11.7m

Financial health · 2025

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

Who owns STO HOLDING AS?

STEINAR OKSVOLD
STO HOLDING AS
NOK 0 rev. · NOK −69,000 profit

STO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STO HOLDING AS own?

STO HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about STO HOLDING AS

Who owns STO HOLDING AS?

STEINAR OKSVOLD is the largest registered owner, with 100.0%.

What is the revenue of STO HOLDING AS?

STO HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of STO HOLDING AS?

Steinar Oksvold is registered as general manager of STO HOLDING AS.

Where is STO HOLDING AS based?

STO HOLDING AS has its business address in Trondheim.

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.