BIZTRAC BETA
Rental and operating of own or leased real estate

STOKNES HOLDING AS

Org. no. 989269879 Limited company (AS) Ålesund Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −19,000
Equity NOK 844,000
Incorporated 2005
Share capital NOK 167,000

Signals

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

STOKNES HOLDING AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 989269879. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 167,000, divided into 22 shares. The company's stated purpose is: “Eie og forvalte aksjer og selskapsandeler i andre selskaper, samt dermed forbunden virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −19,000
Equity
NOK 844,000
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns STOKNES HOLDING AS?

SVEIN OSKAR STOKNES
STOKNES HOLDING AS
NOK 0 rev. · NOK −19,000 profit

STOKNES HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does STOKNES HOLDING AS own?

STOKNES HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STOKNES HOLDING AS

Who owns STOKNES HOLDING AS?

SVEIN OSKAR STOKNES is the largest registered owner, with 45.5%.

What is the revenue of STOKNES HOLDING AS?

STOKNES HOLDING AS had revenue of NOK 0 in 2024.

Where is STOKNES HOLDING AS based?

STOKNES HOLDING AS has its business address in Ålesund.

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.