BIZTRAC BETA
Building of civilian ships and floating structures

ELPRO ELECTRO AS

Org. no. 912972127 Limited company (AS) Indre Fosen Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 201.2m
Operating profit NOK 10.9m
Equity NOK 36.0m
Incorporated 2013
Employees 85
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ELPRO ELECTRO AS is registered as a limited company in Indre Fosen, Trøndelag with organisation number 912972127. The business is classified under building of civilian ships and floating structures (NACE 30.110). The company was incorporated in 2013 and has 85 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Yte maritime tjenester, herunder innrednings- og installasjonsarbeid utført på skip, samt andre tjenester og virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 201.2m in revenue and NOK 10.9m in operating profit.

Key figures · 2024

Revenue
NOK 201.2m
Operating profit
NOK 10.9m
Equity
NOK 36.0m
Est. value
NOK 59.7m

Financial health · 2024

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

Who owns ELPRO ELECTRO AS?

ELPRO GROUP AS
ELPRO ELECTRO AS
NOK 201.2m rev. · NOK 10.9m profit

ELPRO ELECTRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELPRO ELECTRO AS

Who owns ELPRO ELECTRO AS?

ELPRO GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of ELPRO ELECTRO AS?

ELPRO ELECTRO AS had revenue of NOK 201.2m in 2024.

Where is ELPRO ELECTRO AS based?

ELPRO ELECTRO AS has its business address in Rissa.

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.