BIZTRAC BETA
Uoppgitt

THORLEIF AAS HOLDING AS

Org. no. 936326358 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −13
Equity NOK 18,000
Incorporated 2025
Share capital NOK 30,000

Signals

4 flags
  • Driftsunderskudd Siste driftsresultat er negativt (−13 kr).
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2025-09-25.
  • Nylig endring 2026-06-17 Adresseendring registrert 2026-06-17.

THORLEIF AAS HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 936326358. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, samt tilhørende virksomhet.”.

Key figures

Operating profit
NOK −13
Equity
NOK 18,000
Est. value
NOK 22,000

Financial health · 2025

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

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

Who owns THORLEIF AAS HOLDING AS?

MOHAMEDI AZAGOUAGH
THORLEIF AAS HOLDING AS
· NOK −13 profit

THORLEIF AAS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does THORLEIF AAS HOLDING AS own?

THORLEIF AAS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about THORLEIF AAS HOLDING AS

Who owns THORLEIF AAS HOLDING AS?

MOHAMEDI AZAGOUAGH is the largest registered owner, with 100.0%.

Who is the general manager of THORLEIF AAS HOLDING AS?

Mohamedi Azagouagh is registered as general manager of THORLEIF AAS HOLDING AS.

Where is THORLEIF AAS HOLDING AS based?

THORLEIF AAS 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.