BIZTRAC BETA
Uoppgitt

WICKMANN HOLDING AS

Org. no. 830704442 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −15,000
Equity NOK −51,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−51k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−15k kr).

WICKMANN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 830704442. 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: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −15,000
Equity
NOK −51,000

Financial health · 2024

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

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

Who owns WICKMANN HOLDING AS?

OLA WICKMANN
WICKMANN HOLDING AS
· NOK −15,000 profit

WICKMANN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WICKMANN HOLDING AS own?

WICKMANN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WICKMANN HOLDING AS

Who owns WICKMANN HOLDING AS?

OLA WICKMANN is the largest registered owner, with 100.0%.

Who is the general manager of WICKMANN HOLDING AS?

Ola Wickmann is registered as general manager of WICKMANN HOLDING AS.

Where is WICKMANN HOLDING AS based?

WICKMANN HOLDING AS has its business address in Oslo.

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.