BIZTRAC BETA
Sewerage

RØR OG KANALRENS AS

Org. no. 876920492 Limited company (AS) Våler Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 14.3m
Operating profit NOK 1.7m
Equity NOK 4.5m
Incorporated 1996
Employees 6
Share capital NOK 30,000

RØR OG KANALRENS AS is registered as a limited company in Våler, Østfold with organisation number 876920492. The business is classified under sewerage (NACE 37.000). The company was incorporated in 1996 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 400000 shares. The company's stated purpose is: “Renovasjon og tømming av vann- og avløpskummer samt tilhørenede virksomhet. Videre skal selskapet drive rens og service av ventilasjonsanlegg samt tilhørende virksomhet. Selskapet skal kunne delta i andre selskaper. ”. The most recent filed accounts, for the 2024 financial year, show NOK 14.3m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 14.3m
Operating profit
NOK 1.7m
Equity
NOK 4.5m
Est. value
NOK 7.2m

Financial health · 2024

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

Who owns RØR OG KANALRENS AS?

RØR OG KANALRENS HOLDING AS
RØR OG KANALRENS AS
NOK 14.3m rev. · NOK 1.7m profit

RØR OG KANALRENS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RØR OG KANALRENS AS

Who owns RØR OG KANALRENS AS?

RØR OG KANALRENS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RØR OG KANALRENS AS?

RØR OG KANALRENS AS had revenue of NOK 14.3m in 2024.

Who is the general manager of RØR OG KANALRENS AS?

Morten Sten Braaten is registered as general manager of RØR OG KANALRENS AS.

Where is RØR OG KANALRENS AS based?

RØR OG KANALRENS AS has its business address in Våler I Østfold.

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.