biztrac. BETA
COMPANY REGISTER PROFILE
914817765 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Wholesale of wood, construction materials and sanitary equipment

VP BYGG AS

Org. no. 914817765 Limited company (AS) Eidsvoll Incorporated 2015 Active
Revenue 2025 NOK 13.6m
Operating profit NOK 680,000
Equity NOK 757,000
Incorporated 2015
Employees 5
Share capital NOK 30,000

VP BYGG AS is registered as a limited company in Eidsvoll, Akershus with organisation number 914817765. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2015 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Import av diverse byggevarer, vinduer, dører, møbler. Installasjons tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.6m in revenue and NOK 680,000 in operating profit.

Former names: VINDUER PRO AS

Key figures · 2025

Revenue
NOK 13.6m
▲ +22 %
Operating profit
NOK 680,000
▲ +154 %
Equity
NOK 757,000
▲ +124 %
Est. value
NOK 2.7m

Financial health · 2025

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
16.9%
Very good
Return on total assets
Solidity
17.8%
Satisfactory
Equity as a share of total capital

Who owns VP BYGG AS?

VP BYGG AS
NOK 13.6m rev. · NOK 680,000 profit

VP BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VP BYGG AS

Who owns VP BYGG AS?

Donatas Stundzia is the largest registered owner, with 100.0%.

What is the revenue of VP BYGG AS?

VP BYGG AS had revenue of NOK 13.6m in 2025.

Who is the general manager of VP BYGG AS?

Ramunas Stundzia is registered as general manager of VP BYGG AS.

Where is VP BYGG AS based?

VP BYGG AS has its business address in Dal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.