BIZTRAC BETA
Plumbing installation

SNERTINGDAL RØRLEGGERBEDRIFT AS

Org. no. 926826271 Limited company (AS) Gjøvik Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 7.0m
Operating profit NOK 1.0m
Equity NOK 4.1m
Incorporated 2021
Share capital NOK 30,000

SNERTINGDAL RØRLEGGERBEDRIFT AS is registered as a limited company in Gjøvik, Innlandet with organisation number 926826271. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive rørleggervirksomhet, samt kjøp og salg av varer og tjenester som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.0m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 7.0m
Operating profit
NOK 1.0m
Equity
NOK 4.1m
Est. value
NOK 5.3m

Financial health · 2025

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

Who owns SNERTINGDAL RØRLEGGERBEDRIFT AS?

TORMOD HAUGOM
SNERTINGDAL RØRLEGGERBEDRIFT AS
NOK 7.0m rev. · NOK 1.0m profit

SNERTINGDAL RØRLEGGERBEDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SNERTINGDAL RØRLEGGERBEDRIFT AS

Who owns SNERTINGDAL RØRLEGGERBEDRIFT AS?

TORMOD HAUGOM is the largest registered owner, with 100.0%.

What is the revenue of SNERTINGDAL RØRLEGGERBEDRIFT AS?

SNERTINGDAL RØRLEGGERBEDRIFT AS had revenue of NOK 7.0m in 2025.

Who is the general manager of SNERTINGDAL RØRLEGGERBEDRIFT AS?

Tormod Haugom is registered as general manager of SNERTINGDAL RØRLEGGERBEDRIFT AS.

Where is SNERTINGDAL RØRLEGGERBEDRIFT AS based?

SNERTINGDAL RØRLEGGERBEDRIFT AS has its business address in Snertingdal.

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.