BIZTRAC BETA
Other captive investment companies

LEO INVEST AS

Org. no. 987059419 Limited company (AS) Sandefjord Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 82.3m
Operating profit NOK 81.1m
Equity NOK 394.7m
Incorporated 2004
Share capital NOK 1.4m

LEO INVEST AS is registered as a limited company in Sandefjord, Vestfold with organisation number 987059419. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2004. Registered share capital is NOK 1.4m, divided into 127092 shares. The company's stated purpose is: “Å samordne og å ivareta aksjonærenes direkte og indirekte eierinteresse i JOTUN AS, samt å drive investeringsvirksomhet av enhver art.”. The most recent filed accounts, for the 2024 financial year, show NOK 82.3m in revenue and NOK 81.1m in operating profit.

Key figures · 2024

Revenue
NOK 82.3m
Operating profit
NOK 81.1m
Equity
NOK 394.7m
Est. value
NOK 463.1m

Financial health · 2024

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

Who owns LEO INVEST AS?

KARI ANETTE JACOBSEN
LEO INVEST AS
NOK 82.3m rev. · NOK 81.1m profit

LEO INVEST AS has 5 registered shareholders:

All shareholders and roles →

Which companies does LEO INVEST AS own?

LEO INVEST AS holds stakes in 12 companies:

See the full ownership structure →

Frequently asked questions about LEO INVEST AS

Who owns LEO INVEST AS?

KARI ANETTE JACOBSEN is the largest registered owner, with 44.2%.

What is the revenue of LEO INVEST AS?

LEO INVEST AS had revenue of NOK 82.3m in 2024.

Who is the general manager of LEO INVEST AS?

Anders August Jahre is registered as general manager of LEO INVEST AS.

Where is LEO INVEST AS based?

LEO INVEST AS has its business address in Sandefjord.

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.