BIZTRAC BETA
Other captive investment companies

HAFSKJOLD HOLDING AS

Org. no. 989131222 Limited company (AS) Lier Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −122,000
Equity NOK 15.0m
Incorporated 2005
Share capital NOK 1.1m

Signals

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

HAFSKJOLD HOLDING AS is registered as a limited company in Lier, Buskerud with organisation number 989131222. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 1.1m, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av fast eiendom, kjøp og salg av aksjer og annet som naturlig hører inn under dette. ”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −122,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −122,000
Equity
NOK 15.0m
Est. value
NOK 12.2m

Financial health · 2024

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

Who owns HAFSKJOLD HOLDING AS?

TRYGVE HAFSKJOLD
HAFSKJOLD HOLDING AS
NOK 0 rev. · NOK −122,000 profit

HAFSKJOLD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HAFSKJOLD HOLDING AS own?

HAFSKJOLD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HAFSKJOLD HOLDING AS

Who owns HAFSKJOLD HOLDING AS?

TRYGVE HAFSKJOLD is the largest registered owner, with 100.0%.

What is the revenue of HAFSKJOLD HOLDING AS?

HAFSKJOLD HOLDING AS had revenue of NOK 0 in 2024.

Where is HAFSKJOLD HOLDING AS based?

HAFSKJOLD HOLDING AS has its business address in Lier.

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.