BIZTRAC BETA
Retail sale of automotive fuel

BLUE ENERGY HOLDING AS

Org. no. 916252706 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −559,000
Equity NOK 561.1m
Incorporated 2015
Share capital NOK 2.1m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−559k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BLUE ENERGY HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 916252706. The business is classified under retail sale of automotive fuel (NACE 47.300). The company was incorporated in 2015. Registered share capital is NOK 2.1m, divided into 1030000 shares. The company's stated purpose is: “Selskapets virksomhet er 1) handel med og investering i fast eiendom, verdipapirer og andre formuesobjekter, 2) produksjon, fordeling, distribusjon, omsetning og anvendelse av energi og 3) annet som står i naturlig forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −559,000
Equity
NOK 561.1m
Est. value
NOK 701.4m

Financial health · 2024

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

Who owns BLUE ENERGY HOLDING AS?

GREENBIT ENERGY AS
BLUE ENERGY HOLDING AS
· NOK −559,000 profit

BLUE ENERGY HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BLUE ENERGY HOLDING AS own?

BLUE ENERGY HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BLUE ENERGY HOLDING AS

Who owns BLUE ENERGY HOLDING AS?

GREENBIT ENERGY AS is the largest registered owner, with 100.0%.

Where is BLUE ENERGY HOLDING AS based?

BLUE ENERGY HOLDING AS has its business address in Oslo.

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.