BIZTRAC BETA
Plumbing installation

NUMEDAL RØR AS

Org. no. 987726628 Limited company (AS) Nore Og Uvdal Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK −269,000
Equity NOK 5.8m
Incorporated 2004
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−269k kr).

NUMEDAL RØR AS is registered as a limited company in Nore Og Uvdal, Buskerud with organisation number 987726628. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Rørleggervirksomhet og kjøp og salg av varer i forbindelse med rørleggervirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK −269,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK −269,000
Equity
NOK 5.8m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns NUMEDAL RØR AS?

PEDERSEN INVEST AS
NUMEDAL RØR AS
NOK 2.4m rev. · NOK −269,000 profit

NUMEDAL RØR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NUMEDAL RØR AS own?

NUMEDAL RØR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NUMEDAL RØR AS

Who owns NUMEDAL RØR AS?

PEDERSEN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of NUMEDAL RØR AS?

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

Who is the general manager of NUMEDAL RØR AS?

Ronny Pedersen is registered as general manager of NUMEDAL RØR AS.

Where is NUMEDAL RØR AS based?

NUMEDAL RØR AS has its business address in Uvdal.

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.