BIZTRAC BETA
Uoppgitt

VEKSETH HOLDING AS

Org. no. 931882740 Limited company (AS) Snåsa Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −4,000
Equity NOK 26,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

VEKSETH HOLDING AS is registered as a limited company in Snåsa, Trøndelag with organisation number 931882740. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer i aksjer, fast eiendom og andre eiendeler i andre selskap og foretak samt all annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 26,000
Est. value
NOK 30,000

Financial health · 2024

Liquidity
0.86
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
46.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VEKSETH HOLDING AS?

HALDOR VEKSETH
VEKSETH HOLDING AS
NOK 0 rev. · NOK −4,000 profit

VEKSETH HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VEKSETH HOLDING AS own?

VEKSETH HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VEKSETH HOLDING AS

Who owns VEKSETH HOLDING AS?

HALDOR VEKSETH is the largest registered owner, with 100.0%.

What is the revenue of VEKSETH HOLDING AS?

VEKSETH HOLDING AS had revenue of NOK 0 in 2024.

Where is VEKSETH HOLDING AS based?

VEKSETH HOLDING AS has its business address in Snåsa.

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.