BIZTRAC BETA
Other captive investment companies

VALOREM INVEST AS

Org. no. 921162235 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 1.8m
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

VALOREM INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 921162235. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i aksjer, eiendom og alt som det kan investeres i.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 1.8m
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns VALOREM INVEST AS?

TORE ANDRESEN
VALOREM INVEST AS
NOK 0 rev. · NOK −9,000 profit

VALOREM INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VALOREM INVEST AS own?

VALOREM INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VALOREM INVEST AS

Who owns VALOREM INVEST AS?

TORE ANDRESEN is the largest registered owner, with 100.0%.

What is the revenue of VALOREM INVEST AS?

VALOREM INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of VALOREM INVEST AS?

Tore Andresen is registered as general manager of VALOREM INVEST AS.

Where is VALOREM INVEST AS based?

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