BIZTRAC BETA
Other captive investment companies

HORTEMO VENTURES AS

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

Signals

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

HORTEMO VENTURES AS is registered as a limited company in Oslo, Oslo with organisation number 920252842. 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 1 shares. The company's stated purpose is: “Investering i aksjer og andeler, rådgivning og deltagelse i andre virksomheter, programvereutvikling og musikkutøvelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −342,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −342,000
Equity
NOK 12.3m
Est. value
NOK 17.4m

Financial health · 2025

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

Who owns HORTEMO VENTURES AS?

HENRIK HALVORSEN HORTEMO
HORTEMO VENTURES AS
NOK 0 rev. · NOK −342,000 profit

HORTEMO VENTURES AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HORTEMO VENTURES AS own?

HORTEMO VENTURES AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HORTEMO VENTURES AS

Who owns HORTEMO VENTURES AS?

HENRIK HALVORSEN HORTEMO is the largest registered owner, with 100.0%.

What is the revenue of HORTEMO VENTURES AS?

HORTEMO VENTURES AS had revenue of NOK 0 in 2025.

Where is HORTEMO VENTURES AS based?

HORTEMO VENTURES 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.