BIZTRAC BETA
Wholesale of information and communication equipment

CHARGE ENERGY HOLDING AS

Org. no. 934568680 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 1.3m
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

CHARGE ENERGY HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 934568680. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie alle aksjer i Charge Energy AS og gjøre andre investering.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 1.3m
Est. value
NOK 4.5m

Financial health · 2025

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

Who owns CHARGE ENERGY HOLDING AS?

ASLE VENÅS
CHARGE ENERGY HOLDING AS
NOK 0 rev. · NOK −5,000 profit

CHARGE ENERGY HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CHARGE ENERGY HOLDING AS own?

CHARGE ENERGY HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about CHARGE ENERGY HOLDING AS

Who owns CHARGE ENERGY HOLDING AS?

ASLE VENÅS is the largest registered owner, with 100.0%.

What is the revenue of CHARGE ENERGY HOLDING AS?

CHARGE ENERGY HOLDING AS had revenue of NOK 0 in 2025.

Where is CHARGE ENERGY HOLDING AS based?

CHARGE ENERGY HOLDING AS has its business address in Sandvika.

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.