BIZTRAC BETA
Plumbing installation

RØRLEGGERMESTER RUNE HAUG AS

Org. no. 932015072 Limited company (AS) Asker Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 5.8m
Operating profit NOK 1.4m
Equity NOK 30,000
Incorporated 2023
Share capital NOK 30,000

RØRLEGGERMESTER RUNE HAUG AS is registered as a limited company in Asker, Akershus with organisation number 932015072. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Er rørleggertjenester og annen drift i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.8m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 5.8m
Operating profit
NOK 1.4m
Equity
NOK 30,000
Est. value
NOK 3.6m

Financial health · 2025

Liquidity
1.00
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RØRLEGGERMESTER RUNE HAUG AS?

RUNE HAUG HOLDING AS
RØRLEGGERMESTER RUNE HAUG AS
NOK 5.8m rev. · NOK 1.4m profit

RØRLEGGERMESTER RUNE HAUG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RØRLEGGERMESTER RUNE HAUG AS

Who owns RØRLEGGERMESTER RUNE HAUG AS?

RUNE HAUG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RØRLEGGERMESTER RUNE HAUG AS?

RØRLEGGERMESTER RUNE HAUG AS had revenue of NOK 5.8m in 2024.

Who is the general manager of RØRLEGGERMESTER RUNE HAUG AS?

Rune Haug is registered as general manager of RØRLEGGERMESTER RUNE HAUG AS.

Where is RØRLEGGERMESTER RUNE HAUG AS based?

RØRLEGGERMESTER RUNE HAUG AS has its business address in Sætre.

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.