BIZTRAC BETA
Electrical installation

ELPARTNER AS

Org. no. 930153923 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 22.3m
Operating profit NOK 2.6m
Equity NOK 4.2m
Incorporated 2022
Employees 14
Share capital NOK 300,000

ELPARTNER AS is registered as a limited company in Trondheim, Trøndelag with organisation number 930153923. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2022 and has 14 registered employees. Registered share capital is NOK 300,000, divided into 30000 shares. The company's stated purpose is: “Salg, installering, vedlikehold og drift innenfor fagområdet sterkstrøm og svakstrøm, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 22.3m in revenue and NOK 2.6m in operating profit.

Key figures · 2024

Revenue
NOK 22.3m
Operating profit
NOK 2.6m
Equity
NOK 4.2m
Est. value
NOK 9.4m

Financial health · 2024

Liquidity
1.48
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.6%
Good
Equity as a share of total capital

Who owns ELPARTNER AS?

ELPARTNER HOLDING AS
ELPARTNER AS
NOK 22.3m rev. · NOK 2.6m profit

ELPARTNER AS has 5 registered shareholders:

All shareholders and roles →

Which companies does ELPARTNER AS own?

ELPARTNER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ELPARTNER AS

Who owns ELPARTNER AS?

ELPARTNER HOLDING AS is the largest registered owner, with 37.5%.

What is the revenue of ELPARTNER AS?

ELPARTNER AS had revenue of NOK 22.3m in 2024.

Who is the general manager of ELPARTNER AS?

Trond Richart Sivertsen is registered as general manager of ELPARTNER AS.

Where is ELPARTNER AS based?

ELPARTNER 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.