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

VARMTHUS AS

Org. no. 929529944 Limited company (AS) Stord Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK 504,000
Equity NOK 8,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-23 Konkurs registrert 2026-06-23.

VARMTHUS AS is registered as a limited company in Stord, Vestland with organisation number 929529944. The business is classified under refrigeration installation, heat pump installation and installation of fireplaces (NACE 43.222). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg og montering av varmepumper og konsulenttjenester i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK 504,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK 504,000
Equity
NOK 8,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
1.25
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VARMTHUS AS?

HANS INGVAR ROMSLOE
VARMTHUS AS
NOK 4.2m rev. · NOK 504,000 profit

VARMTHUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VARMTHUS AS

Who owns VARMTHUS AS?

HANS INGVAR ROMSLOE is the largest registered owner, with 100.0%.

What is the revenue of VARMTHUS AS?

VARMTHUS AS had revenue of NOK 4.2m in 2024.

Who is the general manager of VARMTHUS AS?

Hans Ingvar Romsloe is registered as general manager of VARMTHUS AS.

Where is VARMTHUS AS based?

VARMTHUS AS has its business address in Stord.

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.