BIZTRAC BETA
Plumbing installation

VÅTROMSPESIALISTEN AS

Org. no. 933175723 Limited company (AS) Drammen Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 7.7m
Operating profit NOK 742,000
Equity NOK 851,000
Incorporated 2024
Share capital NOK 270,000

VÅTROMSPESIALISTEN AS is registered as a limited company in Drammen, Buskerud with organisation number 933175723. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2024. Registered share capital is NOK 270,000, divided into 270000 shares. The company's stated purpose is: “Tilby rørleggertjenester, inkludert, men ikke begrenset til, installasjon, reparasjon og vedlikehold av sanitær, oppvarming, og vann- og avløpssystemer i boliger, kommersielle bygninger, og industrielle anlegg.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.7m in revenue and NOK 742,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.7m
Operating profit
NOK 742,000
Equity
NOK 851,000
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns VÅTROMSPESIALISTEN AS?

FUNKMODUL AS
VÅTROMSPESIALISTEN AS
NOK 7.7m rev. · NOK 742,000 profit

VÅTROMSPESIALISTEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VÅTROMSPESIALISTEN AS

Who owns VÅTROMSPESIALISTEN AS?

FUNKMODUL AS is the largest registered owner, with 50.0%.

What is the revenue of VÅTROMSPESIALISTEN AS?

VÅTROMSPESIALISTEN AS had revenue of NOK 7.7m in 2024.

Who is the general manager of VÅTROMSPESIALISTEN AS?

Morten Guldbrand is registered as general manager of VÅTROMSPESIALISTEN AS.

Where is VÅTROMSPESIALISTEN AS based?

VÅTROMSPESIALISTEN AS has its business address in Mjøndalen.

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.