BIZTRAC BETA
Steam and air conditioning supply

BILLINGSTAD ENERGI AS

Org. no. 921660944 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 6.1m
Operating profit NOK −259,000
Equity NOK 10.8m
Incorporated 2018
Share capital NOK 2.4m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−259k kr).

BILLINGSTAD ENERGI AS is registered as a limited company in Oslo, Oslo with organisation number 921660944. The business is classified under steam and air conditioning supply (NACE 35.300). The company was incorporated in 2018. Registered share capital is NOK 2.4m, divided into 2400998 shares. The company's stated purpose is: “Utvikle og eie anlegg for bærekraftig energiforsyning samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.1m in revenue and NOK −259,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.1m
Operating profit
NOK −259,000
Equity
NOK 10.8m
Est. value
NOK 11.8m

Financial health · 2024

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

Who owns BILLINGSTAD ENERGI AS?

JM NORGE AS
BILLINGSTAD ENERGI AS
NOK 6.1m rev. · NOK −259,000 profit

BILLINGSTAD ENERGI AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BILLINGSTAD ENERGI AS

Who owns BILLINGSTAD ENERGI AS?

JM NORGE AS is the largest registered owner, with 30.3%.

What is the revenue of BILLINGSTAD ENERGI AS?

BILLINGSTAD ENERGI AS had revenue of NOK 6.1m in 2024.

Who is the general manager of BILLINGSTAD ENERGI AS?

Even Gjelsås is registered as general manager of BILLINGSTAD ENERGI AS.

Where is BILLINGSTAD ENERGI AS based?

BILLINGSTAD ENERGI 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.