BIZTRAC BETA
Buying and selling of own real estate

EPSILON PRIVATE EQUITY AS

Org. no. 994705415 Limited company (AS) Bærum Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 331,000
Operating profit NOK 304,000
Equity NOK 1.0m
Incorporated 2009
Share capital NOK 100,000

EPSILON PRIVATE EQUITY AS is registered as a limited company in Bærum, Akershus with organisation number 994705415. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Å yte investeringstjenester og tilknyttede tjenester, samt annen virksomhet som står i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 331,000 in revenue and NOK 304,000 in operating profit.

Key figures · 2024

Revenue
NOK 331,000
Operating profit
NOK 304,000
Equity
NOK 1.0m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns EPSILON PRIVATE EQUITY AS?

JON OLAV MJØLHUS
EPSILON PRIVATE EQUITY AS
NOK 331,000 rev. · NOK 304,000 profit

EPSILON PRIVATE EQUITY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EPSILON PRIVATE EQUITY AS

Who owns EPSILON PRIVATE EQUITY AS?

JON OLAV MJØLHUS is the largest registered owner, with 100.0%.

What is the revenue of EPSILON PRIVATE EQUITY AS?

EPSILON PRIVATE EQUITY AS had revenue of NOK 331,000 in 2024.

Who is the general manager of EPSILON PRIVATE EQUITY AS?

Jon Olav Mjølhus is registered as general manager of EPSILON PRIVATE EQUITY AS.

Where is EPSILON PRIVATE EQUITY AS based?

EPSILON PRIVATE EQUITY AS has its business address in Høvik.

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.