BIZTRAC BETA
Construction of residential and non-residential buildings

VVR BYGG AS

Org. no. 913134036 Limited company (AS) Nordre Follo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 22,000
Equity NOK 24,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-03-18 Adresseendring registrert 2026-03-18.

VVR BYGG AS is registered as a limited company in Nordre Follo, Akershus with organisation number 913134036. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er bygning tjenester, rådgivning innen bygningsprosjekter og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 22,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 22,000
Equity
NOK 24,000
Est. value
NOK 75,000

Financial health · 2025

Liquidity
1.65
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VVR BYGG AS?

VALERIJS VAIVODS
VVR BYGG AS
NOK 1.8m rev. · NOK 22,000 profit

VVR BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VVR BYGG AS

Who owns VVR BYGG AS?

VALERIJS VAIVODS is the largest registered owner, with 55.0%.

What is the revenue of VVR BYGG AS?

VVR BYGG AS had revenue of NOK 1.8m in 2025.

Who is the general manager of VVR BYGG AS?

Valerijs Vaivods is registered as general manager of VVR BYGG AS.

Where is VVR BYGG AS based?

VVR BYGG AS has its business address in Siggerud.

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.