BIZTRAC BETA
Wholesale of other machinery and equipment

HEAT CON VARMETEKNIKK AS

Org. no. 917081301 Limited company (AS) Oslo Incorporated 1932 Active
Ownership graph ↗
Revenue 2024 NOK 21.7m
Operating profit NOK 1.2m
Equity NOK 6.1m
Incorporated 1932
Employees 5
Share capital NOK 156,000

HEAT CON VARMETEKNIKK AS is registered as a limited company in Oslo, Oslo with organisation number 917081301. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 1932 and has 5 registered employees. Registered share capital is NOK 156,000, divided into 5000 shares. The company's stated purpose is: “Handel, import/eksport og alt som står i forbindelse hermed, herunder eiendomsdrift og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.7m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 21.7m
Operating profit
NOK 1.2m
Equity
NOK 6.1m
Est. value
NOK 7.7m

Financial health · 2024

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

Who owns HEAT CON VARMETEKNIKK AS?

CHAPEAU AS
HEAT CON VARMETEKNIKK AS
NOK 21.7m rev. · NOK 1.2m profit

HEAT CON VARMETEKNIKK AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about HEAT CON VARMETEKNIKK AS

Who owns HEAT CON VARMETEKNIKK AS?

CHAPEAU AS is the largest registered owner, with 57.0%.

What is the revenue of HEAT CON VARMETEKNIKK AS?

HEAT CON VARMETEKNIKK AS had revenue of NOK 21.7m in 2024.

Who is the general manager of HEAT CON VARMETEKNIKK AS?

Karl Axel Kluge Svendsen is registered as general manager of HEAT CON VARMETEKNIKK AS.

Where is HEAT CON VARMETEKNIKK AS based?

HEAT CON VARMETEKNIKK 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.