biztrac. BETA
COMPANY REGISTER PROFILE
991123970 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

LIVERMORE INVEST AS

Org. no. 991123970 Limited company (AS) Bærum Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 39.7m
Operating profit NOK 39.5m
Equity NOK 103.9m
Incorporated 2007
Share capital NOK 100,000

LIVERMORE INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 991123970. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1 shares. The company's stated purpose is: “Investering i aksjer og andre finansielle instrumenter, samt andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 39.7m in revenue and NOK 39.5m in operating profit.

Key figures · 2025

Revenue
NOK 39.7m
▲ +520 %
Operating profit
NOK 39.5m
▲ +545 %
Equity
NOK 103.9m
▲ +49 %
Est. value
NOK 132.5m

Financial health · 2025

Liquidity
4.63
Very good
Current assets ÷ current liabilities
Profitability
36.4%
Very good
Return on total assets
Solidity
78.5%
Very good
Equity as a share of total capital

Who owns LIVERMORE INVEST AS?

LIVERMORE INVEST AS
NOK 39.7m rev. · NOK 39.5m profit

LIVERMORE INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LIVERMORE INVEST AS own?

LIVERMORE INVEST AS holds stakes in 16 companies:

See the full ownership structure →

Frequently asked questions about LIVERMORE INVEST AS

Who owns LIVERMORE INVEST AS?

Stian Folker Larsen is the largest registered owner, with 100.0%.

What is the revenue of LIVERMORE INVEST AS?

LIVERMORE INVEST AS had revenue of NOK 39.7m in 2025.

Where is LIVERMORE INVEST AS based?

LIVERMORE INVEST AS has its business address in Blommenholm.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.