BIZTRAC BETA
Fund management activities

EXPLORE EQUITY AS

Org. no. 914837901 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 30.8m
Operating profit NOK 11.4m
Equity NOK 13.8m
Incorporated 2015
Employees 6
Share capital NOK 632,000

EXPLORE EQUITY AS is registered as a limited company in Oslo, Oslo with organisation number 914837901. The business is classified under fund management activities (NACE 66.300). The company was incorporated in 2015 and has 6 registered employees. Registered share capital is NOK 632,000, divided into 63158 shares. The company's stated purpose is: “Forvalte alternative investeringsfond, samt tjenester og virksomhet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 30.8m in revenue and NOK 11.4m in operating profit.

Key figures · 2025

Revenue
NOK 30.8m
Operating profit
NOK 11.4m
Equity
NOK 13.8m
Est. value
NOK 36.9m

Financial health · 2025

Liquidity
1.18
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.7%
Good
Equity as a share of total capital

Who owns EXPLORE EQUITY AS?

TIBERIUS AS
EXPLORE EQUITY AS
NOK 30.8m rev. · NOK 11.4m profit

EXPLORE EQUITY AS has 3 registered shareholders:

All shareholders and roles →

Which companies does EXPLORE EQUITY AS own?

EXPLORE EQUITY AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about EXPLORE EQUITY AS

Who owns EXPLORE EQUITY AS?

TIBERIUS AS is the largest registered owner, with 47.5%.

What is the revenue of EXPLORE EQUITY AS?

EXPLORE EQUITY AS had revenue of NOK 30.8m in 2025.

Who is the general manager of EXPLORE EQUITY AS?

Henrik Lisæth is registered as general manager of EXPLORE EQUITY AS.

Where is EXPLORE EQUITY AS based?

EXPLORE EQUITY 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.