BIZTRAC BETA
Plumbing installation

NORSK RØRLEGGERSERVICE AS

Org. no. 933634868 Limited company (AS) Stange Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 284,000
Equity NOK 209,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-30 Adresseendring registrert 2026-06-30.

NORSK RØRLEGGERSERVICE AS is registered as a limited company in Stange, Innlandet with organisation number 933634868. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rørleggerarbeid og salg av varer og tjenester som faller under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 284,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 284,000
Equity
NOK 209,000
Est. value
NOK 886,000

Financial health · 2025

Liquidity
1.43
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.1%
Good
Equity as a share of total capital

Who owns NORSK RØRLEGGERSERVICE AS?

ISAK ØVERLI MELVÆR
NORSK RØRLEGGERSERVICE AS
NOK 2.4m rev. · NOK 284,000 profit

NORSK RØRLEGGERSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORSK RØRLEGGERSERVICE AS

Who owns NORSK RØRLEGGERSERVICE AS?

ISAK ØVERLI MELVÆR is the largest registered owner, with 100.0%.

What is the revenue of NORSK RØRLEGGERSERVICE AS?

NORSK RØRLEGGERSERVICE AS had revenue of NOK 2.4m in 2025.

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

Isak Øverli Melvær is registered as general manager of NORSK RØRLEGGERSERVICE AS.

Where is NORSK RØRLEGGERSERVICE AS based?

NORSK RØRLEGGERSERVICE AS has its business address in Ottestad.

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.