BIZTRAC BETA
Uoppgitt

INSTANES HOLDING AS

Org. no. 989205145 Limited company (AS) Ullensvang Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 3.0m
Incorporated 2005
Share capital NOK 1.2m

Signals

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

INSTANES HOLDING AS is registered as a limited company in Ullensvang, Vestland with organisation number 989205145. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 1.2m, divided into 120 shares. The company's stated purpose is: “Selskapet sitt føremål er å investere i norske og nordiske føretak. Selskapet kan også gjennom aksjekjøp eller på andre måtar engasjera seg i andre føretak uansett føremål og selskapsform.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 3.0m
Est. value
NOK 5.0m

Financial health · 2025

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

Who owns INSTANES HOLDING AS?

TOR INSTANES
INSTANES HOLDING AS
NOK 0 rev. · NOK −13,000 profit

INSTANES HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does INSTANES HOLDING AS own?

INSTANES HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about INSTANES HOLDING AS

Who owns INSTANES HOLDING AS?

TOR INSTANES is the largest registered owner, with 100.0%.

What is the revenue of INSTANES HOLDING AS?

INSTANES HOLDING AS had revenue of NOK 0 in 2025.

Where is INSTANES HOLDING AS based?

INSTANES HOLDING AS has its business address in Kinsarvik.

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.