BIZTRAC BETA
Refrigeration installation, heat pump installation and installation of fireplaces

WAAGE VARMETEKNIKK AS

Org. no. 925903825 Limited company (AS) Kristiansund Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 107,000
Equity NOK 480,000
Incorporated 2020
Share capital NOK 100,000

WAAGE VARMETEKNIKK AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 925903825. The business is classified under refrigeration installation, heat pump installation and installation of fireplaces (NACE 43.222). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg, montering og service og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 107,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 107,000
Equity
NOK 480,000
Est. value
NOK 571,000

Financial health · 2025

Liquidity
1.42
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.3%
Good
Equity as a share of total capital

Who owns WAAGE VARMETEKNIKK AS?

HAAVARD WAAGE
WAAGE VARMETEKNIKK AS
NOK 2.9m rev. · NOK 107,000 profit

WAAGE VARMETEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WAAGE VARMETEKNIKK AS

Who owns WAAGE VARMETEKNIKK AS?

HAAVARD WAAGE is the largest registered owner, with 100.0%.

What is the revenue of WAAGE VARMETEKNIKK AS?

WAAGE VARMETEKNIKK AS had revenue of NOK 2.9m in 2025.

Who is the general manager of WAAGE VARMETEKNIKK AS?

Haavard Waage is registered as general manager of WAAGE VARMETEKNIKK AS.

Where is WAAGE VARMETEKNIKK AS based?

WAAGE VARMETEKNIKK AS has its business address in Frei.

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.