BIZTRAC BETA
Plumbing installation

VIKA RØR AS

Org. no. 987028238 Limited company (AS) Gran Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 12.9m
Operating profit NOK 1.4m
Equity NOK 2.8m
Incorporated 2004
Employees 11
Share capital NOK 100,000

VIKA RØR AS is registered as a limited company in Gran, Innlandet with organisation number 987028238. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2004 and has 11 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Rørleggervirksomhet/forretning og annen virksomhet som naturlig hører inn under dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.9m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 12.9m
Operating profit
NOK 1.4m
Equity
NOK 2.8m
Est. value
NOK 5.7m

Financial health · 2024

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

Who owns VIKA RØR AS?

JOHN ANDERS KVÆRNERUD NESBAKKEN
VIKA RØR AS
NOK 12.9m rev. · NOK 1.4m profit

VIKA RØR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIKA RØR AS own?

VIKA RØR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VIKA RØR AS

Who owns VIKA RØR AS?

JOHN ANDERS KVÆRNERUD NESBAKKEN is the largest registered owner, with 100.0%.

What is the revenue of VIKA RØR AS?

VIKA RØR AS had revenue of NOK 12.9m in 2024.

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

John Anders Kværnerud Nesbakken is registered as general manager of VIKA RØR AS.

Where is VIKA RØR AS based?

VIKA RØR AS has its business address in Brandbu.

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.