BIZTRAC BETA
E45 ATERMA AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Other technical consultancy

E45 ATERMA AS

Org. no. 988805955 Limited company (AS) Ringerike Incorporated 2005 Bankrupt
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK 199,000
Equity NOK 745,000
Incorporated 2005
Share capital NOK 150,000

Signals

2 flags
  • Konkurs Selskapet er registrert konkurs i Enhetsregisteret.
  • Nylig endring 2026-07-18 Konkurs registrert 2026-07-18.

E45 ATERMA AS is registered as a limited company in Ringerike, Buskerud with organisation number 988805955. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2005. Registered share capital is NOK 150,000, divided into 100 shares. The company's stated purpose is: “Identifisere, utvikle, bygge og drifte mikro- og minikraftverk samt investeringsvirksomhet innen kraftsektoren i Norge og kjøp og salg av relaterte varer, utstyr og tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK 199,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK 199,000
Equity
NOK 745,000
Est. value
NOK 1.2m

Financial health · 2024

Liquidity
-0.70
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.7%
Good
Equity as a share of total capital

Who owns E45 ATERMA AS?

JARLE SIGMUND LYSBERG
E45 ATERMA AS
NOK 3.7m rev. · NOK 199,000 profit

E45 ATERMA AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about E45 ATERMA AS

Who owns E45 ATERMA AS?

JARLE SIGMUND LYSBERG is the largest registered owner, with 42.0%.

What is the revenue of E45 ATERMA AS?

E45 ATERMA AS had revenue of NOK 3.7m in 2024.

Where is E45 ATERMA AS based?

E45 ATERMA AS has its business address in Hønefoss.

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.