BIZTRAC BETA
Plumbing installation

NORSK RØRTEKNIKK AS

Org. no. 997461193 Limited company (AS) Asker Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 6.1m
Operating profit NOK 9,000
Equity NOK 1.5m
Incorporated 2011
Share capital NOK 102,000

NORSK RØRTEKNIKK AS is registered as a limited company in Asker, Akershus with organisation number 997461193. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2011. Registered share capital is NOK 102,000, divided into 102 shares. The company's stated purpose is: “Vannlekkasjelytting, rørfornying, oppfresing av tette anboringer, tining av frosne rør, krotstrømpereparasjoner av rør og annet arbeide relatert til alle typer vann-, kloakk- og overvannsrør. Herunder deltakelse i andre selskap med tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.1m in revenue and NOK 9,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.1m
Operating profit
NOK 9,000
Equity
NOK 1.5m
Est. value
NOK 768,000

Financial health · 2024

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

Who owns NORSK RØRTEKNIKK AS?

KRISTIAN GULLHAV
NORSK RØRTEKNIKK AS
NOK 6.1m rev. · NOK 9,000 profit

NORSK RØRTEKNIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORSK RØRTEKNIKK AS

Who owns NORSK RØRTEKNIKK AS?

KRISTIAN GULLHAV is the largest registered owner, with 75.5%.

What is the revenue of NORSK RØRTEKNIKK AS?

NORSK RØRTEKNIKK AS had revenue of NOK 6.1m in 2025.

Who is the general manager of NORSK RØRTEKNIKK AS?

Kristian Gullhav is registered as general manager of NORSK RØRTEKNIKK AS.

Where is NORSK RØRTEKNIKK AS based?

NORSK RØRTEKNIKK AS has its business address in Nesbru.

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.