BIZTRAC BETA
Steam and air conditioning supply

ULSTEIN FJERNVARME AS

Org. no. 996957152 Limited company (AS) Ulstein Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK −1.9m
Equity NOK 12.5m
Incorporated 2011
Share capital NOK 31.5m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,9 mill kr).

ULSTEIN FJERNVARME AS is registered as a limited company in Ulstein, Møre og Romsdal with organisation number 996957152. The business is classified under steam and air conditioning supply (NACE 35.300). The company was incorporated in 2011. Registered share capital is NOK 31.5m, divided into 31500 shares. The company's stated purpose is: “Etablering av infrastruktur og drifting av fjernvarmeanlegg i Ulsteinvik sentrum.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK −1.9m in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK −1.9m
Equity
NOK 12.5m
Est. value
NOK 13.8m

Financial health · 2024

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

Who owns ULSTEIN FJERNVARME AS?

ULSTEIN KOMMUNE
ULSTEIN FJERNVARME AS
NOK 3.6m rev. · NOK −1.9m profit

ULSTEIN FJERNVARME AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ULSTEIN FJERNVARME AS

Who owns ULSTEIN FJERNVARME AS?

ULSTEIN KOMMUNE is the largest registered owner, with 100.0%.

What is the revenue of ULSTEIN FJERNVARME AS?

ULSTEIN FJERNVARME AS had revenue of NOK 3.6m in 2024.

Who is the general manager of ULSTEIN FJERNVARME AS?

Jarl Martin Møller is registered as general manager of ULSTEIN FJERNVARME AS.

Where is ULSTEIN FJERNVARME AS based?

ULSTEIN FJERNVARME AS has its business address in Ulsteinvik.

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.