BIZTRAC BETA
COMPANY REGISTER PROFILE
911915197 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

HENFALLET HOLDING AS

Org. no. 911915197 Limited company (AS) Tydal Incorporated 2013 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK −113,000
Incorporated 2013
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−113k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

HENFALLET HOLDING AS is registered as a limited company in Tydal, Trøndelag with organisation number 911915197. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av aksjer, samt drive konsulentvirksomhet. Herunder å delta i andre selskap med lignende virksomhet eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2025

Operating profit
NOK −9,000
▼ −5 %
Equity
NOK −113,000
▼ −9 %

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-74.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HENFALLET HOLDING AS?

HENFALLET HOLDING AS
· NOK −9,000 profit

HENFALLET HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HENFALLET HOLDING AS own?

HENFALLET HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HENFALLET HOLDING AS

Who owns HENFALLET HOLDING AS?

INGE SVELMO is the largest registered owner, with 100.0%.

Where is HENFALLET HOLDING AS based?

HENFALLET HOLDING AS has its business address in Tydal.

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

Report a problem

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