BIZTRAC BETA
General cleaning of buildings

PROSJEKT VASK AS

Org. no. 916642237 Limited company (AS) Larvik Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 13.5m
Operating profit NOK 584,000
Equity NOK 753,000
Incorporated 2016
Employees 25
Share capital NOK 30,000

PROSJEKT VASK AS is registered as a limited company in Larvik, Vestfold with organisation number 916642237. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2016 and has 25 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Renholdstjenester og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.5m in revenue and NOK 584,000 in operating profit.

Key figures · 2024

Revenue
NOK 13.5m
Operating profit
NOK 584,000
Equity
NOK 753,000
Est. value
NOK 2.7m

Financial health · 2024

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.6%
Good
Equity as a share of total capital

Who owns PROSJEKT VASK AS?

EDVIN VESTGÅRD
PROSJEKT VASK AS
NOK 13.5m rev. · NOK 584,000 profit

PROSJEKT VASK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PROSJEKT VASK AS

Who owns PROSJEKT VASK AS?

EDVIN VESTGÅRD is the largest registered owner, with 50.0%.

What is the revenue of PROSJEKT VASK AS?

PROSJEKT VASK AS had revenue of NOK 13.5m in 2024.

Who is the general manager of PROSJEKT VASK AS?

Pål Berntsen is registered as general manager of PROSJEKT VASK AS.

Where is PROSJEKT VASK AS based?

PROSJEKT VASK AS has its business address in Tjodalyng.

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.