biztrac. BETA
COMPANY REGISTER PROFILE
931071254 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Sewerage

RØR OG KANALRENS HOLDING AS

Org. no. 931071254 Limited company (AS) Våler Incorporated 2023 Active
Operating profit NOK −11,000
Equity NOK 91,000
Incorporated 2023
Share capital NOK 45,000

Signals

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

RØR OG KANALRENS HOLDING AS is registered as a limited company in Våler, Østfold with organisation number 931071254. The business is classified under sewerage (NACE 37.000). The company was incorporated in 2023. Registered share capital is NOK 45,000, divided into 45 shares. The company's stated purpose is: “Investering i, og utvikling av andre selskaper.”.

Key figures · 2025

Operating profit
NOK −11,000
▲ +40 %
Equity
NOK 91,000
▲ +8 %
Est. value
NOK 169,000

Financial health · 2025

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
0.8%
Not satisfactory
Return on total assets
Solidity
2.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RØR OG KANALRENS HOLDING AS?

RØR OG KANALRENS HOLDING AS
· NOK −11,000 profit

RØR OG KANALRENS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RØR OG KANALRENS HOLDING AS own?

RØR OG KANALRENS HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RØR OG KANALRENS HOLDING AS

Who owns RØR OG KANALRENS HOLDING AS?

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

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

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

Where is RØR OG KANALRENS HOLDING AS based?

RØR OG KANALRENS HOLDING 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.