BIZTRAC BETA
Buying and selling of own real estate

VIGOR PROSJEKT AS

Org. no. 924429275 Limited company (AS) Etne Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −36,000
Equity NOK 612,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

VIGOR PROSJEKT AS is registered as a limited company in Etne, Vestland with organisation number 924429275. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −36,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −36,000
Equity
NOK 612,000
Est. value
NOK 559,000

Financial health · 2025

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

Who owns VIGOR PROSJEKT AS?

HATO HOLDING AS
VIGOR PROSJEKT AS
NOK 0 rev. · NOK −36,000 profit

VIGOR PROSJEKT AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VIGOR PROSJEKT AS own?

VIGOR PROSJEKT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VIGOR PROSJEKT AS

Who owns VIGOR PROSJEKT AS?

HATO HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of VIGOR PROSJEKT AS?

VIGOR PROSJEKT AS had revenue of NOK 0 in 2025.

Who is the general manager of VIGOR PROSJEKT AS?

Kjetil Nedreskår is registered as general manager of VIGOR PROSJEKT AS.

Where is VIGOR PROSJEKT AS based?

VIGOR PROSJEKT AS has its business address in Etne.

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.