BIZTRAC BETA
Plumbing installation

PROSJEKT TEKNIKK AS

Org. no. 988662666 Limited company (AS) Nesbyen Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 2,000
Operating profit NOK −14,000
Equity NOK 139,000
Incorporated 2005
Share capital NOK 100,000

Signals

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

PROSJEKT TEKNIKK AS is registered as a limited company in Nesbyen, Buskerud with organisation number 988662666. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Rørleggervirksomhet, utleie av arbeidskraft, investeringer i eiendom, aksjer og andre kapitalvarer, samt alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2,000 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 2,000
Operating profit
NOK −14,000
Equity
NOK 139,000
Est. value
NOK 76,000

Financial health · 2025

Liquidity
-54.20
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
135.8%
Very good
Equity as a share of total capital

Who owns PROSJEKT TEKNIKK AS?

LARS VESTHEIM
PROSJEKT TEKNIKK AS
NOK 2,000 rev. · NOK −14,000 profit

PROSJEKT TEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROSJEKT TEKNIKK AS

Who owns PROSJEKT TEKNIKK AS?

LARS VESTHEIM is the largest registered owner, with 100.0%.

What is the revenue of PROSJEKT TEKNIKK AS?

PROSJEKT TEKNIKK AS had revenue of NOK 2,000 in 2025.

Who is the general manager of PROSJEKT TEKNIKK AS?

Lars Vestheim is registered as general manager of PROSJEKT TEKNIKK AS.

Where is PROSJEKT TEKNIKK AS based?

PROSJEKT TEKNIKK AS has its business address in Nesbyen.

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.