BIZTRAC BETA
Other captive investment companies

STRONGHOLD CAPITAL AS

Org. no. 933493466 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 1.6m
Incorporated 2024
Share capital NOK 1.6m

Signals

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

STRONGHOLD CAPITAL AS is registered as a limited company in Oslo, Oslo with organisation number 933493466. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2024. Registered share capital is NOK 1.6m, divided into 155000 shares. The company's stated purpose is: “Fungere som et investeringsselskap og det som står i naturlig forbindelse med dette, herunder fremtidig salg av investeringene.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 1.6m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns STRONGHOLD CAPITAL AS?

MAGNUS NAGLESTAD
STRONGHOLD CAPITAL AS
NOK 0 rev. · NOK −5,000 profit

STRONGHOLD CAPITAL AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about STRONGHOLD CAPITAL AS

Who owns STRONGHOLD CAPITAL AS?

MAGNUS NAGLESTAD is the largest registered owner, with 32.3%.

What is the revenue of STRONGHOLD CAPITAL AS?

STRONGHOLD CAPITAL AS had revenue of NOK 0 in 2025.

Who is the general manager of STRONGHOLD CAPITAL AS?

Thomas Vikenes is registered as general manager of STRONGHOLD CAPITAL AS.

Where is STRONGHOLD CAPITAL AS based?

STRONGHOLD 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.