BIZTRAC BETA
Uoppgitt

WOLLAN HOLDING AS

Org. no. 923626948 Limited company (AS) Vennesla Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −1,000
Equity NOK 30,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

WOLLAN HOLDING AS is registered as a limited company in Vennesla, Agder with organisation number 923626948. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i og utvikle andre selskaper gjennom kjøp, eie og salg av alle typer aksjer og andeler og alt som naturlig henger sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK 30,000
Est. value
NOK 73,000

Financial health · 2025

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

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

Who owns WOLLAN HOLDING AS?

SIRI TERESE WOLLAN QUISPE
WOLLAN HOLDING AS
NOK 0 rev. · NOK −1,000 profit

WOLLAN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WOLLAN HOLDING AS own?

WOLLAN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WOLLAN HOLDING AS

Who owns WOLLAN HOLDING AS?

SIRI TERESE WOLLAN QUISPE is the largest registered owner, with 100.0%.

What is the revenue of WOLLAN HOLDING AS?

WOLLAN HOLDING AS had revenue of NOK 0 in 2025.

Where is WOLLAN HOLDING AS based?

WOLLAN HOLDING AS has its business address in Vennesla.

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.