BIZTRAC BETA
Uoppgitt

ASKELADDEN CAPITAL AS

Org. no. 922431043 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK −7.8m
Equity NOK 29.3m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7,8 mill kr).

ASKELADDEN CAPITAL AS is registered as a limited company in Oslo, Oslo with organisation number 922431043. 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: “Investering i andre selskaper gjennom aksjer, andeler eller på annen måte, samt hva derved står i sammenheng.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK −7.8m in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK −7.8m
Equity
NOK 29.3m
Est. value
NOK 34.5m

Financial health · 2024

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

Who owns ASKELADDEN CAPITAL AS?

OSCAR ALEXANDER GARMANN WILHELMSEN
ASKELADDEN CAPITAL AS
NOK 5.3m rev. · NOK −7.8m profit

ASKELADDEN CAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ASKELADDEN CAPITAL AS own?

ASKELADDEN CAPITAL AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ASKELADDEN CAPITAL AS

Who owns ASKELADDEN CAPITAL AS?

OSCAR ALEXANDER GARMANN WILHELMSEN is the largest registered owner, with 100.0%.

What is the revenue of ASKELADDEN CAPITAL AS?

ASKELADDEN CAPITAL AS had revenue of NOK 5.3m in 2024.

Where is ASKELADDEN CAPITAL AS based?

ASKELADDEN CAPITAL 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.