BIZTRAC BETA
Plumbing installation

SVOLVÆR RØR AS

Org. no. 989117548 Limited company (AS) Vågan Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 7.3m
Operating profit NOK 491,000
Equity NOK 1.3m
Incorporated 2005
Share capital NOK 220,000

SVOLVÆR RØR AS is registered as a limited company in Vågan, Nordland with organisation number 989117548. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2005. Registered share capital is NOK 220,000, divided into 220 shares. The company's stated purpose is: “Forretning innen VVS-bransjen, varme- og sanitærarbeide, VA-arbeide, industri, nyanlegg, kjerneboring, plastsveising, rehabilitering, samt annet som naturlig hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.3m in revenue and NOK 491,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.3m
Operating profit
NOK 491,000
Equity
NOK 1.3m
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns SVOLVÆR RØR AS?

SVOLVÆR RØR EIENDOM AS
SVOLVÆR RØR AS
NOK 7.3m rev. · NOK 491,000 profit

SVOLVÆR RØR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SVOLVÆR RØR AS own?

SVOLVÆR RØR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SVOLVÆR RØR AS

Who owns SVOLVÆR RØR AS?

SVOLVÆR RØR EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SVOLVÆR RØR AS?

SVOLVÆR RØR AS had revenue of NOK 7.3m in 2024.

Who is the general manager of SVOLVÆR RØR AS?

Berit Mellem is registered as general manager of SVOLVÆR RØR AS.

Where is SVOLVÆR RØR AS based?

SVOLVÆR RØR AS has its business address in Laupstad.

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.