BIZTRAC BETA
Plumbing installation

MOELV RØRSERVICE AS

Org. no. 983196551 Limited company (AS) Ringsaker Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 28.1m
Operating profit NOK 1.6m
Equity NOK 8.9m
Incorporated 2001
Employees 12
Share capital NOK 220,000

MOELV RØRSERVICE AS is registered as a limited company in Ringsaker, Innlandet with organisation number 983196551. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2001 and has 12 registered employees. Registered share capital is NOK 220,000, divided into 220 shares. The company's stated purpose is: “Rørleggervirksomhet, service, salg og virksomhet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.1m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 28.1m
Operating profit
NOK 1.6m
Equity
NOK 8.9m
Est. value
NOK 10.2m

Financial health · 2024

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

Who owns MOELV RØRSERVICE AS?

RMO HOLDING AS
MOELV RØRSERVICE AS
NOK 28.1m rev. · NOK 1.6m profit

MOELV RØRSERVICE AS has 6 registered shareholders:

All shareholders and roles →

Which companies does MOELV RØRSERVICE AS own?

MOELV RØRSERVICE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MOELV RØRSERVICE AS

Who owns MOELV RØRSERVICE AS?

RMO HOLDING AS is the largest registered owner, with 25.0%.

What is the revenue of MOELV RØRSERVICE AS?

MOELV RØRSERVICE AS had revenue of NOK 28.1m in 2024.

Who is the general manager of MOELV RØRSERVICE AS?

Stian Granseth is registered as general manager of MOELV RØRSERVICE AS.

Where is MOELV RØRSERVICE AS based?

MOELV RØRSERVICE AS has its business address in Moelv.

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.