BIZTRAC BETA
Trade of electricity

FORTUM HEDGING AS

Org. no. 970938974 Limited company (AS) Oslo Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 51.9m
Operating profit NOK 26.7m
Equity NOK 653.4m
Incorporated 1994
Employees 11
Share capital NOK 50.0m

FORTUM HEDGING AS is registered as a limited company in Oslo, Oslo with organisation number 970938974. The business is classified under trade of electricity (NACE 35.150). The company was incorporated in 1994 and has 11 registered employees. Registered share capital is NOK 50.0m, divided into 2000000 shares. The company's stated purpose is: “Handel med fysiske og finansielle kraftkontrakter og kraftderivater, samt andre finansielle energidervater og dervater på utslippskvoter, for egen regning eller på vegne av andre etter nærmere avtale.”. The most recent filed accounts, for the 2024 financial year, show NOK 51.9m in revenue and NOK 26.7m in operating profit.

Key figures · 2024

Revenue
NOK 51.9m
Operating profit
NOK 26.7m
Equity
NOK 653.4m
Est. value
NOK 513.1m

Financial health · 2024

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

Who owns FORTUM HEDGING AS?

FORTUM CONSUMER SOLUTIONS AS
FORTUM HEDGING AS
NOK 51.9m rev. · NOK 26.7m profit

FORTUM HEDGING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FORTUM HEDGING AS

Who owns FORTUM HEDGING AS?

FORTUM CONSUMER SOLUTIONS AS is the largest registered owner, with 100.0%.

What is the revenue of FORTUM HEDGING AS?

FORTUM HEDGING AS had revenue of NOK 51.9m in 2024.

Who is the general manager of FORTUM HEDGING AS?

Juha Markus Sebastian Sundberg is registered as general manager of FORTUM HEDGING AS.

Where is FORTUM HEDGING AS based?

FORTUM HEDGING 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.