BIZTRAC BETA
Plumbing installation

VANG RØR AS

Org. no. 918216669 Limited company (AS) Vang Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 3.3m
Operating profit NOK 468,000
Equity NOK 1.6m
Incorporated 2016
Share capital NOK 200,000

VANG RØR AS is registered as a limited company in Vang, Innlandet with organisation number 918216669. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2016. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Rørleggervirksomhet og andre produkter og tjenester som naturlig hører til dette, herunder å delta i andre selskap med liknende virksomhet, og kjøp og slag av aksjer eller på annen måte gjøre deg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.3m in revenue and NOK 468,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.3m
Operating profit
NOK 468,000
Equity
NOK 1.6m
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns VANG RØR AS?

VANG MASKIN AS
VANG RØR AS
NOK 3.3m rev. · NOK 468,000 profit

VANG RØR AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VANG RØR AS own?

VANG RØR AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VANG RØR AS

Who owns VANG RØR AS?

VANG MASKIN AS is the largest registered owner, with 51.0%.

What is the revenue of VANG RØR AS?

VANG RØR AS had revenue of NOK 3.3m in 2024.

Who is the general manager of VANG RØR AS?

Egil Karlsen is registered as general manager of VANG RØR AS.

Where is VANG RØR AS based?

VANG RØR AS has its business address in Vang I Valdres.

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.