BIZTRAC BETA
Other captive investment companies

LEVANTOR INVEST HOLDING AS

Org. no. 925386286 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −147,000
Equity NOK 701.2m
Incorporated 2020
Share capital NOK 42,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−147k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LEVANTOR INVEST HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 925386286. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2020. Registered share capital is NOK 42,000, divided into 10000 shares. The company's stated purpose is: “Eie aksjer og andeler i selskaper hvis hovedvirksomhet er å yte tjenester relatert til kapitalforvaltning og/eller investeringsrådgivning, samt aktiviteter i naturlig sammenheng med dette.”.

Key figures · 2024

Operating profit
NOK −147,000
Equity
NOK 701.2m
Est. value
NOK 639.9m

Financial health · 2024

Liquidity
0.13
Not satisfactory
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 LEVANTOR INVEST HOLDING AS?

JOCO AS
LEVANTOR INVEST HOLDING AS
· NOK −147,000 profit

LEVANTOR INVEST HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LEVANTOR INVEST HOLDING AS own?

LEVANTOR INVEST HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LEVANTOR INVEST HOLDING AS

Who owns LEVANTOR INVEST HOLDING AS?

JOCO AS is the largest registered owner, with 55.0%.

Where is LEVANTOR INVEST HOLDING AS based?

LEVANTOR INVEST 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.