BIZTRAC BETA
Plumbing installation

HALLINGDAL VARME & SANITÆR AS

Org. no. 984058039 Limited company (AS) Nesbyen Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 8.3m
Operating profit NOK −16.8m
Equity NOK 6.8m
Incorporated 2001
Share capital NOK 700,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−16,8 mill kr).
  • Nylig endring 2026-03-10 Adresseendring registrert 2026-03-10.

HALLINGDAL VARME & SANITÆR AS is registered as a limited company in Nesbyen, Buskerud with organisation number 984058039. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2001. Registered share capital is NOK 700,000, divided into 7000 shares. The company's stated purpose is: “Handel, produksjon og tjenesteyting, samt hva dermed står i forbindelse, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.3m in revenue and NOK −16.8m in operating profit.

Key figures · 2024

Revenue
NOK 8.3m
Operating profit
NOK −16.8m
Equity
NOK 6.8m
Est. value
NOK 5.8m

Financial health · 2024

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

Who owns HALLINGDAL VARME & SANITÆR AS?

ASSEMBLIN AS
HALLINGDAL VARME & SANITÆR AS
NOK 8.3m rev. · NOK −16.8m profit

HALLINGDAL VARME & SANITÆR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HALLINGDAL VARME & SANITÆR AS

Who owns HALLINGDAL VARME & SANITÆR AS?

ASSEMBLIN AS is the largest registered owner, with 100.0%.

What is the revenue of HALLINGDAL VARME & SANITÆR AS?

HALLINGDAL VARME & SANITÆR AS had revenue of NOK 8.3m in 2024.

Where is HALLINGDAL VARME & SANITÆR AS based?

HALLINGDAL VARME & SANITÆR AS has its business address in Nesbyen.

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.