BIZTRAC BETA
Electrical installation

EL-INSTALLASJON INNLANDET AS

Org. no. 928621251 Limited company (AS) Lillehammer Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 54.6m
Operating profit NOK 7.2m
Equity NOK 12.2m
Incorporated 2022
Employees 24
Share capital NOK 300,000

EL-INSTALLASJON INNLANDET AS is registered as a limited company in Lillehammer, Innlandet with organisation number 928621251. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2022 and has 24 registered employees. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Elektroinstallasjon og annen virksomhet som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 54.6m in revenue and NOK 7.2m in operating profit.

Key figures · 2024

Revenue
NOK 54.6m
Operating profit
NOK 7.2m
Equity
NOK 12.2m
Est. value
NOK 27.1m

Financial health · 2024

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

Who owns EL-INSTALLASJON INNLANDET AS?

DRUGIS HOLDING AS
EL-INSTALLASJON INNLANDET AS
NOK 54.6m rev. · NOK 7.2m profit

EL-INSTALLASJON INNLANDET AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about EL-INSTALLASJON INNLANDET AS

Who owns EL-INSTALLASJON INNLANDET AS?

DRUGIS HOLDING AS is the largest registered owner, with 30.0%.

What is the revenue of EL-INSTALLASJON INNLANDET AS?

EL-INSTALLASJON INNLANDET AS had revenue of NOK 54.6m in 2024.

Who is the general manager of EL-INSTALLASJON INNLANDET AS?

Espen Englund Stumlien is registered as general manager of EL-INSTALLASJON INNLANDET AS.

Where is EL-INSTALLASJON INNLANDET AS based?

EL-INSTALLASJON INNLANDET AS has its business address in Lillehammer.

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.