BIZTRAC BETA
Manufacture of other builders' carpentry and joinery

VADSET HOLDING AS

Org. no. 932277115 Limited company (AS) Ålesund Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −43,000
Equity NOK 9.1m
Incorporated 2023
Share capital NOK 33,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−43k kr).

VADSET HOLDING AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 932277115. The business is classified under manufacture of other builders' carpentry and joinery (NACE 16.230). The company was incorporated in 2023. Registered share capital is NOK 33,000, divided into 220 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, verdipapirer eller annen virksomhet, samt erverv, utvikling, forvaltning, omsetning og utleie av fast eiendom, selv eller gjennom hel- eller deleide selskaper.”.

Key figures · 2024

Operating profit
NOK −43,000
Equity
NOK 9.1m
Est. value
NOK 10.7m

Financial health · 2024

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

Who owns VADSET HOLDING AS?

FURLIA AS
VADSET HOLDING AS
· NOK −43,000 profit

VADSET HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does VADSET HOLDING AS own?

VADSET HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VADSET HOLDING AS

Who owns VADSET HOLDING AS?

FURLIA AS is the largest registered owner, with 40.9%.

Who is the general manager of VADSET HOLDING AS?

Øyvind Vadset is registered as general manager of VADSET HOLDING AS.

Where is VADSET HOLDING AS based?

VADSET HOLDING AS has its business address in Skodje.

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.