BIZTRAC BETA
Rental and operating of own or leased real estate

ILA INVEST HOLDING AS

Org. no. 917607338 Limited company (AS) Trondheim Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 127,000
Operating profit NOK 4,000
Equity NOK 322,000
Incorporated 2016
Share capital NOK 30,000

ILA INVEST HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 917607338. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Forvalte eierinteresser, foreta investeringer og tilby administrative tjenester, samt all annen virksomhet som henger sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 127,000 in revenue and NOK 4,000 in operating profit.

Key figures · 2025

Revenue
NOK 127,000
Operating profit
NOK 4,000
Equity
NOK 322,000
Est. value
NOK 230,000

Financial health · 2025

Liquidity
1.18
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.1%
Weak
Equity as a share of total capital

Who owns ILA INVEST HOLDING AS?

ERLEND NESS
ILA INVEST HOLDING AS
NOK 127,000 rev. · NOK 4,000 profit

ILA INVEST HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ILA INVEST HOLDING AS own?

ILA INVEST HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ILA INVEST HOLDING AS

Who owns ILA INVEST HOLDING AS?

ERLEND NESS is the largest registered owner, with 100.0%.

What is the revenue of ILA INVEST HOLDING AS?

ILA INVEST HOLDING AS had revenue of NOK 127,000 in 2025.

Where is ILA INVEST HOLDING AS based?

ILA INVEST 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.