BIZTRAC BETA
Other captive investment companies

EHL INVEST AS

Org. no. 913039351 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 2.3m
Equity NOK 12.2m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-07 Aksjekapital registrert 2026-07-07.

EHL INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 913039351. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Eie aksjer og/eller andeler i PricewaterhouseCoopers, i tillegg til at selskapet kan inneha andre finansielle eiendeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 2.3m
Equity
NOK 12.2m
Est. value
NOK 13.7m

Financial health · 2025

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

Who owns EHL INVEST AS?

ERIK HOLMÉN
EHL INVEST AS
NOK 2.3m rev. · NOK 2.3m profit

EHL INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EHL INVEST AS own?

EHL INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EHL INVEST AS

Who owns EHL INVEST AS?

ERIK HOLMÉN is the largest registered owner, with 100.0%.

What is the revenue of EHL INVEST AS?

EHL INVEST AS had revenue of NOK 2.3m in 2025.

Who is the general manager of EHL INVEST AS?

Erik Holmén is registered as general manager of EHL INVEST AS.

Where is EHL INVEST AS based?

EHL 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.