BIZTRAC BETA
Plumbing installation

RØRLEGGERMESTER OVEN AS

Org. no. 819505322 Limited company (AS) Råde Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 3.2m
Operating profit NOK 825,000
Equity NOK 896,000
Incorporated 2017
Share capital NOK 30,000

RØRLEGGERMESTER OVEN AS is registered as a limited company in Råde, Østfold with organisation number 819505322. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rørleggervirksomhet og annet som faller naturlig inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.2m in revenue and NOK 825,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.2m
Operating profit
NOK 825,000
Equity
NOK 896,000
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns RØRLEGGERMESTER OVEN AS?

TROND OVEN
RØRLEGGERMESTER OVEN AS
NOK 3.2m rev. · NOK 825,000 profit

RØRLEGGERMESTER OVEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RØRLEGGERMESTER OVEN AS own?

RØRLEGGERMESTER OVEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RØRLEGGERMESTER OVEN AS

Who owns RØRLEGGERMESTER OVEN AS?

TROND OVEN is the largest registered owner, with 100.0%.

What is the revenue of RØRLEGGERMESTER OVEN AS?

RØRLEGGERMESTER OVEN AS had revenue of NOK 3.2m in 2024.

Who is the general manager of RØRLEGGERMESTER OVEN AS?

Trond Oven is registered as general manager of RØRLEGGERMESTER OVEN AS.

Where is RØRLEGGERMESTER OVEN AS based?

RØRLEGGERMESTER OVEN AS has its business address in Rygge.

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.