BIZTRAC BETA
Other captive investment companies

WESENBERG VERDISPAR AS

Org. no. 989002325 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −17,000
Equity NOK 21.7m
Incorporated 2005
Share capital NOK 504,000

Signals

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

WESENBERG VERDISPAR AS is registered as a limited company in Bergen, Vestland with organisation number 989002325. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 504,000, divided into 1713 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av fast eiendom, samt erverve og selge aksjer og verdipapirer eller på annen måte gjøre seg interessert i annen virksomhet. Selskapet kan også drive handel og hva dermed naturlig står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −17,000
Equity
NOK 21.7m
Est. value
NOK 19.8m

Financial health · 2024

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

Who owns WESENBERG VERDISPAR AS?

KJELL WESENBERG
WESENBERG VERDISPAR AS
· NOK −17,000 profit

WESENBERG VERDISPAR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WESENBERG VERDISPAR AS own?

WESENBERG VERDISPAR AS holds stakes in 10 companies:

See the full ownership structure →

Frequently asked questions about WESENBERG VERDISPAR AS

Who owns WESENBERG VERDISPAR AS?

KJELL WESENBERG is the largest registered owner, with 100.0%.

Who is the general manager of WESENBERG VERDISPAR AS?

Kjell Wesenberg is registered as general manager of WESENBERG VERDISPAR AS.

Where is WESENBERG VERDISPAR AS based?

WESENBERG VERDISPAR AS has its business address in Bergen.

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.