BIZTRAC BETA
Plumbing installation

VVS SERVICE RUNE BERGE AS

Org. no. 987839082 Limited company (AS) Fjaler Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 7.6m
Operating profit NOK 680,000
Equity NOK 10.1m
Incorporated 2005
Share capital NOK 146,000

VVS SERVICE RUNE BERGE AS is registered as a limited company in Fjaler, Vestland with organisation number 987839082. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2005. Registered share capital is NOK 146,000, divided into 146 shares. The company's stated purpose is: “Drive røyrleggjarverksemd og det som dermed står i tilknyting, herunder ved innskot av kapital, eventuelt ved aksjeteikning å delta i andre verksemder.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.6m in revenue and NOK 680,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.6m
Operating profit
NOK 680,000
Equity
NOK 10.1m
Est. value
NOK 7.0m

Financial health · 2024

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

Who owns VVS SERVICE RUNE BERGE AS?

RUNE HELGE BERGE
VVS SERVICE RUNE BERGE AS
NOK 7.6m rev. · NOK 680,000 profit

VVS SERVICE RUNE BERGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VVS SERVICE RUNE BERGE AS own?

VVS SERVICE RUNE BERGE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VVS SERVICE RUNE BERGE AS

Who owns VVS SERVICE RUNE BERGE AS?

RUNE HELGE BERGE is the largest registered owner, with 100.0%.

What is the revenue of VVS SERVICE RUNE BERGE AS?

VVS SERVICE RUNE BERGE AS had revenue of NOK 7.6m in 2024.

Where is VVS SERVICE RUNE BERGE AS based?

VVS SERVICE RUNE BERGE AS has its business address in Hellevik I Fjaler.

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.