BIZTRAC BETA
Plumbing installation

RØRVERKET AS

Org. no. 991845771 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 9.1m
Operating profit NOK −186,000
Equity NOK 1.2m
Incorporated 2007
Employees 7
Share capital NOK 220,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−186k kr).

RØRVERKET AS is registered as a limited company in Oslo, Oslo with organisation number 991845771. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2007 and has 7 registered employees. Registered share capital is NOK 220,000, divided into 220 shares. The company's stated purpose is: “Drive rørleggervirksomhet og dertil alt som står i forbindelse med sådan virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.1m in revenue and NOK −186,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.1m
Operating profit
NOK −186,000
Equity
NOK 1.2m
Est. value
NOK 3.7m

Financial health · 2024

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

Who owns RØRVERKET AS?

KARLSRUD RØR AS
RØRVERKET AS
NOK 9.1m rev. · NOK −186,000 profit

RØRVERKET AS has 5 registered shareholders:

All shareholders and roles →

Which companies does RØRVERKET AS own?

RØRVERKET AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RØRVERKET AS

Who owns RØRVERKET AS?

KARLSRUD RØR AS is the largest registered owner, with 49.5%.

What is the revenue of RØRVERKET AS?

RØRVERKET AS had revenue of NOK 9.1m in 2024.

Who is the general manager of RØRVERKET AS?

Ole Jacob Isaksen is registered as general manager of RØRVERKET AS.

Where is RØRVERKET AS based?

RØRVERKET AS has its business address in Oslo.

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.