BIZTRAC BETA
Other captive investment companies

SKISTAD AS

Org. no. 998535611 Limited company (AS) Overhalla Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −46,000
Equity NOK 10.6m
Incorporated 2012
Share capital NOK 400,000

Signals

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

SKISTAD AS is registered as a limited company in Overhalla, Trøndelag with organisation number 998535611. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2012. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Å investere i aksjer, andre finansielle investeringer samt eiendom og alt som står i forbindelse med denne type virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −46,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −46,000
Equity
NOK 10.6m
Est. value
NOK 10.2m

Financial health · 2025

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

Who owns SKISTAD AS?

HÅVARD SKISTAD
SKISTAD AS
NOK 0 rev. · NOK −46,000 profit

SKISTAD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKISTAD AS own?

SKISTAD AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SKISTAD AS

Who owns SKISTAD AS?

HÅVARD SKISTAD is the largest registered owner, with 100.0%.

What is the revenue of SKISTAD AS?

SKISTAD AS had revenue of NOK 0 in 2025.

Who is the general manager of SKISTAD AS?

Håvard Skistad is registered as general manager of SKISTAD AS.

Where is SKISTAD AS based?

SKISTAD AS has its business address in Overhalla.

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.