BIZTRAC BETA
Plumbing installation

RÅDE RØRLEGGERSERVICE AS

Org. no. 990590168 Limited company (AS) Moss Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 579,000
Equity NOK 565,000
Incorporated 2006
Share capital NOK 30,000

RÅDE RØRLEGGERSERVICE AS is registered as a limited company in Moss, Østfold with organisation number 990590168. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2006. Registered share capital is NOK 30,000, divided into 500 shares. The company's stated purpose is: “Rørleggervirksomhet, service utenomhus, vann og avløp handel, samt all virksomhet som står i forbindelse med dette. Selskapet vil også ha interesse i kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 579,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK 579,000
Equity
NOK 565,000
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns RÅDE RØRLEGGERSERVICE AS?

ISAK AMUNDSEN
RÅDE RØRLEGGERSERVICE AS
NOK 3.4m rev. · NOK 579,000 profit

RÅDE RØRLEGGERSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RÅDE RØRLEGGERSERVICE AS

Who owns RÅDE RØRLEGGERSERVICE AS?

ISAK AMUNDSEN is the largest registered owner, with 100.0%.

What is the revenue of RÅDE RØRLEGGERSERVICE AS?

RÅDE RØRLEGGERSERVICE AS had revenue of NOK 3.4m in 2025.

Who is the general manager of RÅDE RØRLEGGERSERVICE AS?

Isak Amundsen is registered as general manager of RÅDE RØRLEGGERSERVICE AS.

Where is RÅDE RØRLEGGERSERVICE AS based?

RÅDE RØRLEGGERSERVICE 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.