BIZTRAC BETA
Plumbing installation

VØYENENGA RØR AS

Org. no. 895211192 Limited company (AS) Bærum Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK −19,000
Equity NOK 944,000
Incorporated 2010
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−19k kr).

VØYENENGA RØR AS is registered as a limited company in Bærum, Akershus with organisation number 895211192. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av tjenester og produkter innen VVS bransjen. Investering i eiendom. Enn videre ved aksjekjøp eller på annen måte gjøre seg interessert i andre foretagende med samme eller andre formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.3m in revenue and NOK −19,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.3m
Operating profit
NOK −19,000
Equity
NOK 944,000
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns VØYENENGA RØR AS?

FRED HAMMEREN
VØYENENGA RØR AS
NOK 4.3m rev. · NOK −19,000 profit

VØYENENGA RØR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VØYENENGA RØR AS

Who owns VØYENENGA RØR AS?

FRED HAMMEREN is the largest registered owner, with 51.0%.

What is the revenue of VØYENENGA RØR AS?

VØYENENGA RØR AS had revenue of NOK 4.3m in 2025.

Who is the general manager of VØYENENGA RØR AS?

Fred Hammeren is registered as general manager of VØYENENGA RØR AS.

Where is VØYENENGA RØR AS based?

VØYENENGA RØR AS has its business address in Vøyenenga.

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.