BIZTRAC BETA
Other captive investment companies

FOSENHUS HOLDING AS

Org. no. 834148102 Limited company (AS) Ørland Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK 18.5m
Incorporated 2024
Share capital NOK 175,000

Signals

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

FOSENHUS HOLDING AS is registered as a limited company in Ørland, Trøndelag with organisation number 834148102. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2024. Registered share capital is NOK 175,000, divided into 500 shares. The company's stated purpose is: “Investering i aksjer og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 18.5m
Est. value
NOK 16.9m

Financial health · 2024

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

Who owns FOSENHUS HOLDING AS?

HÅVARD SUNDSETH
FOSENHUS HOLDING AS
NOK 0 rev. · NOK −6,000 profit

FOSENHUS HOLDING AS has 10 registered shareholders:

All shareholders and roles →

Which companies does FOSENHUS HOLDING AS own?

FOSENHUS HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about FOSENHUS HOLDING AS

Who owns FOSENHUS HOLDING AS?

HÅVARD SUNDSETH is the largest registered owner, with 52.0%.

What is the revenue of FOSENHUS HOLDING AS?

FOSENHUS HOLDING AS had revenue of NOK 0 in 2024.

Where is FOSENHUS HOLDING AS based?

FOSENHUS HOLDING AS has its business address in Bjugn.

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.