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

VARMEHUSET AS

Org. no. 984198272 Limited company (AS) Drammen Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 9.9m
Operating profit NOK 1.2m
Equity NOK 3.1m
Incorporated 2001
Share capital NOK 83,000

VARMEHUSET AS is registered as a limited company in Drammen, Buskerud with organisation number 984198272. The business is classified under refrigeration installation, heat pump installation and installation of fireplaces (NACE 43.222). The company was incorporated in 2001. Registered share capital is NOK 83,000, divided into 11020 shares. The company's stated purpose is: “Entreprenørvirksomhet innen bygg- og anleggsvirksomhet, deltakelse i andre selskaper, utleie av fast eiendom, eiendomsbesittelse, investering i aksjer og alt hva derved er forbundet.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.9m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 9.9m
Operating profit
NOK 1.2m
Equity
NOK 3.1m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns VARMEHUSET AS?

TOM EEK LOLLIK-ANDERSEN
VARMEHUSET AS
NOK 9.9m rev. · NOK 1.2m profit

VARMEHUSET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VARMEHUSET AS

Who owns VARMEHUSET AS?

TOM EEK LOLLIK-ANDERSEN is the largest registered owner, with 50.0%.

What is the revenue of VARMEHUSET AS?

VARMEHUSET AS had revenue of NOK 9.9m in 2024.

Who is the general manager of VARMEHUSET AS?

Tom Eek Lollik-Andersen is registered as general manager of VARMEHUSET AS.

Where is VARMEHUSET AS based?

VARMEHUSET AS has its business address in Drammen.

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.