BIZTRAC BETA
Other captive investment companies

LEO CAPITAL AS

Org. no. 994758519 Limited company (AS) Bergen Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 13.9m
Operating profit NOK 12.6m
Equity NOK 27.3m
Incorporated 2009
Share capital NOK 30,000

LEO CAPITAL AS is registered as a limited company in Bergen, Vestland with organisation number 994758519. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2009. Registered share capital is NOK 30,000, divided into 390 shares. The company's stated purpose is: “Forvaltning av fast eiendom, løsøre og verdipapirer, samt ved aksjer og parter å delta i andre selskaper og virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.9m in revenue and NOK 12.6m in operating profit.

Key figures · 2024

Revenue
NOK 13.9m
Operating profit
NOK 12.6m
Equity
NOK 27.3m
Est. value
NOK 49.4m

Financial health · 2024

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

Who owns LEO CAPITAL AS?

ALEXANDRE NIKOLAEVICH LEONCHANKA
LEO CAPITAL AS
NOK 13.9m rev. · NOK 12.6m profit

LEO CAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LEO CAPITAL AS own?

LEO CAPITAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LEO CAPITAL AS

Who owns LEO CAPITAL AS?

ALEXANDRE NIKOLAEVICH LEONCHANKA is the largest registered owner, with 100.0%.

What is the revenue of LEO CAPITAL AS?

LEO CAPITAL AS had revenue of NOK 13.9m in 2024.

Who is the general manager of LEO CAPITAL AS?

Alexandre Nikolaevich Leonchanka is registered as general manager of LEO CAPITAL AS.

Where is LEO CAPITAL AS based?

LEO CAPITAL AS has its business address in Bergen.

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.