biztrac. BETA
COMPANY REGISTER PROFILE
989245473 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

SIGDESTAD HOLDING AS

Org. no. 989245473 Limited company (AS) Kinn Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −23,000
Equity NOK 5.5m
Incorporated 2005
Share capital NOK 390,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−23k kr).
  • Nylig endring 2026-06-30 Adresseendring registrert 2026-06-30.

SIGDESTAD HOLDING AS is registered as a limited company in Kinn, Vestland with organisation number 989245473. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 390,000, divided into 390 shares. The company's stated purpose is: “Investeringsvirksomhet herunder å eie aksjer og andeler i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −23,000
▲ +30 %
Equity
NOK 5.5m
▲ +23 %
Est. value
NOK 6.7m

Financial health · 2025

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

Who owns SIGDESTAD HOLDING AS?

SIGDESTAD HOLDING AS
· NOK −23,000 profit

SIGDESTAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIGDESTAD HOLDING AS own?

SIGDESTAD HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SIGDESTAD HOLDING AS

Who owns SIGDESTAD HOLDING AS?

Kjell Arne Sigdestad is the largest registered owner, with 100.0%.

Who is the general manager of SIGDESTAD HOLDING AS?

Kjell Arne Sigdestad is registered as general manager of SIGDESTAD HOLDING AS.

Where is SIGDESTAD HOLDING AS based?

SIGDESTAD HOLDING AS has its business address in Florø.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.