BIZTRAC BETA
Business and other management consultancy activities

VILDET AS

Org. no. 989238345 Limited company (AS) Haugesund Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 681,000
Operating profit NOK −307,000
Equity NOK 17.7m
Incorporated 2005
Share capital NOK 170,000

Signals

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

VILDET AS is registered as a limited company in Haugesund, Rogaland with organisation number 989238345. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 170,000, divided into 50660 shares. The company's stated purpose is: “Konsulentvirksomhet, investere i andre selskaper, investere i fast eiendom, event med utleie av biler og båter, samt kjøp og salg av motorkjøretøyer samt annet som står i forbindelse hertil.”. The most recent filed accounts, for the 2025 financial year, show NOK 681,000 in revenue and NOK −307,000 in operating profit.

Key figures · 2025

Revenue
NOK 681,000
Operating profit
NOK −307,000
Equity
NOK 17.7m
Est. value
NOK 87.8m

Financial health · 2025

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

Who owns VILDET AS?

ASLE SKJÆRSTAD
VILDET AS
NOK 681,000 rev. · NOK −307,000 profit

VILDET AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VILDET AS own?

VILDET AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about VILDET AS

Who owns VILDET AS?

ASLE SKJÆRSTAD is the largest registered owner, with 75.0%.

What is the revenue of VILDET AS?

VILDET AS had revenue of NOK 681,000 in 2025.

Where is VILDET AS based?

VILDET AS has its business address in Haugesund.

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.