BIZTRAC BETA
Activities of adventure companies

WENDELBO AKTIV HOLDING AS

Org. no. 926334735 Limited company (AS) Moskenes Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 45,000
Incorporated 2020
Share capital NOK 50,000

Signals

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

WENDELBO AKTIV HOLDING AS is registered as a limited company in Moskenes, Nordland with organisation number 926334735. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2020. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Investering i aksjer og andeler i andre selskaper samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −5,000
Equity
NOK 45,000
Est. value
NOK 57,000

Financial health · 2024

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

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

Who owns WENDELBO AKTIV HOLDING AS?

HALLGEIR HENÆS WENDELBO
WENDELBO AKTIV HOLDING AS
· NOK −5,000 profit

WENDELBO AKTIV HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WENDELBO AKTIV HOLDING AS own?

WENDELBO AKTIV HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about WENDELBO AKTIV HOLDING AS

Who owns WENDELBO AKTIV HOLDING AS?

HALLGEIR HENÆS WENDELBO is the largest registered owner, with 100.0%.

Who is the general manager of WENDELBO AKTIV HOLDING AS?

Hallgeir Henæs Wendelbo is registered as general manager of WENDELBO AKTIV HOLDING AS.

Where is WENDELBO AKTIV HOLDING AS based?

WENDELBO AKTIV HOLDING AS has its business address in Sørvågen.

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.