BIZTRAC BETA
Plumbing installation

CW RØR HOLDING AS

Org. no. 920559034 Limited company (AS) Nittedal Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −48,000
Equity NOK −175,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−175k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−48k kr).

CW RØR HOLDING AS is registered as a limited company in Nittedal, Akershus with organisation number 920559034. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Rørleggertjenester og investering i aksjer og eiendom, samt annen aktivitet som naturlig faller sammen med dette herunder deltagelse i andre selskaper med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −48,000
Equity
NOK −175,000

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-303.4%
Weak
Equity as a share of total capital

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

Who owns CW RØR HOLDING AS?

CHRISTIAN WINTHER NIELSEN
CW RØR HOLDING AS
· NOK −48,000 profit

CW RØR HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CW RØR HOLDING AS own?

CW RØR HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CW RØR HOLDING AS

Who owns CW RØR HOLDING AS?

CHRISTIAN WINTHER NIELSEN is the largest registered owner, with 100.0%.

Who is the general manager of CW RØR HOLDING AS?

Christian Winther Nielsen is registered as general manager of CW RØR HOLDING AS.

Where is CW RØR HOLDING AS based?

CW RØR HOLDING AS has its business address in Hakadal.

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.