BIZTRAC BETA
Other captive investment companies

MATS NILSEN HOLDING AS

Org. no. 989233432 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 1.0m
Incorporated 2005
Share capital NOK 300,000

Signals

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

MATS NILSEN HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 989233432. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved å samarbeide med andre virksomheter å forestå investeringsvirksomhet, eiendomsforvaltning og annen virksomhet beslektet med denne inklusive konsulentvirksomhet.”.

Key figures · 2024

Operating profit
NOK −6,000
Equity
NOK 1.0m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns MATS NILSEN HOLDING AS?

MATS NILSEN HOVDAL
MATS NILSEN HOLDING AS
· NOK −6,000 profit

MATS NILSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MATS NILSEN HOLDING AS own?

MATS NILSEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MATS NILSEN HOLDING AS

Who owns MATS NILSEN HOLDING AS?

MATS NILSEN HOVDAL is the largest registered owner, with 100.0%.

Who is the general manager of MATS NILSEN HOLDING AS?

Mats Nilsen Hovdal is registered as general manager of MATS NILSEN HOLDING AS.

Where is MATS NILSEN HOLDING AS based?

MATS NILSEN HOLDING AS has its business address in Trondheim.

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.