BIZTRAC BETA
Other captive investment companies

SIGURD STENDAL AS

Org. no. 992295031 Limited company (AS) Trondheim Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −23,000
Equity NOK 15.8m
Incorporated 2008
Share capital NOK 100,000

Signals

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

SIGURD STENDAL AS is registered as a limited company in Trondheim, Trøndelag with organisation number 992295031. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Utvikling og salg av produkter og tjenester og alt som står i forbindelse med dette, samt deltakelse og investering i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −23,000
Equity
NOK 15.8m
Est. value
NOK 14.6m

Financial health · 2024

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

Who owns SIGURD STENDAL AS?

SIGURD STENDAL
SIGURD STENDAL AS
NOK 0 rev. · NOK −23,000 profit

SIGURD STENDAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIGURD STENDAL AS own?

SIGURD STENDAL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SIGURD STENDAL AS

Who owns SIGURD STENDAL AS?

SIGURD STENDAL is the largest registered owner, with 100.0%.

What is the revenue of SIGURD STENDAL AS?

SIGURD STENDAL AS had revenue of NOK 0 in 2024.

Where is SIGURD STENDAL AS based?

SIGURD STENDAL 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.