BIZTRAC BETA
Manufacture of electricity distribution and control apparatus

ELCAM AS

Org. no. 968341375 Limited company (AS) Hamar Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 19.7m
Operating profit NOK 510,000
Equity NOK 2.5m
Incorporated 1993
Employees 10
Share capital NOK 300,000

Signals

1 flags
  • Nylig endring 2026-04-17 Aksjekapital registrert 2026-04-17.

ELCAM AS is registered as a limited company in Hamar, Innlandet with organisation number 968341375. The business is classified under manufacture of electricity distribution and control apparatus (NACE 27.120). The company was incorporated in 1993 and has 10 registered employees. Registered share capital is NOK 300,000, divided into 300000 shares. The company's stated purpose is: “Konstruksjon, produksjon og salg av elektriske produkter og annet utstyr som er beslektet med dette, også aksjetegning eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 19.7m in revenue and NOK 510,000 in operating profit.

Key figures · 2025

Revenue
NOK 19.7m
Operating profit
NOK 510,000
Equity
NOK 2.5m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns ELCAM AS?

3BSL AS
ELCAM AS
NOK 19.7m rev. · NOK 510,000 profit

ELCAM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELCAM AS

Who owns ELCAM AS?

3BSL AS is the largest registered owner, with 100.0%.

What is the revenue of ELCAM AS?

ELCAM AS had revenue of NOK 19.7m in 2025.

Who is the general manager of ELCAM AS?

Roland Kringsjå Stenhaug is registered as general manager of ELCAM AS.

Where is ELCAM AS based?

ELCAM AS has its business address in Hamar.

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.