BIZTRAC BETA
Civil engineering activities

VAKO PROSJEKT AS

Org. no. 998535034 Limited company (AS) Lier Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 9.4m
Operating profit NOK 544,000
Equity NOK 4.7m
Incorporated 2012
Share capital NOK 45,000

VAKO PROSJEKT AS is registered as a limited company in Lier, Buskerud with organisation number 998535034. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2012. Registered share capital is NOK 45,000, divided into 30 shares. The company's stated purpose is: “Prosjektledelse og økonomiske tjenester. Det skal være anledning til å eie aksjer og andeler i andre selskaper, samt hva herved står naturlig i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.4m in revenue and NOK 544,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.4m
Operating profit
NOK 544,000
Equity
NOK 4.7m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns VAKO PROSJEKT AS?

VAKO PROSJEKT AS
VAKO PROSJEKT AS
NOK 9.4m rev. · NOK 544,000 profit

VAKO PROSJEKT AS has 3 registered shareholders:

All shareholders and roles →

Which companies does VAKO PROSJEKT AS own?

VAKO PROSJEKT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VAKO PROSJEKT AS

Who owns VAKO PROSJEKT AS?

VAKO PROSJEKT AS is the largest registered owner, with 33.3%.

What is the revenue of VAKO PROSJEKT AS?

VAKO PROSJEKT AS had revenue of NOK 9.4m in 2024.

Who is the general manager of VAKO PROSJEKT AS?

Ingar Vatndal is registered as general manager of VAKO PROSJEKT AS.

Where is VAKO PROSJEKT AS based?

VAKO PROSJEKT AS has its business address in Lier.

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.