BIZTRAC BETA
COMPANY REGISTER PROFILE
925355577 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

EROS HOLDING AS

Org. no. 925355577 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Equity NOK 11,000
Incorporated 2020
Share capital NOK 30,000

EROS HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 925355577. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsselskap.”.

Former names: HEALTH4YOU AS

Key figures · 2025

Equity
NOK 11,000
Est. value
NOK 13,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns EROS HOLDING AS?

EROS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EROS HOLDING AS own?

EROS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EROS HOLDING AS

Who owns EROS HOLDING AS?

EIRIK RØNNINGSTAD OLSEN is the largest registered owner, with 100.0%.

Where is EROS HOLDING AS based?

EROS HOLDING AS has its business address in Oslo.

Property

Business address c/o Eirik Rønningstad Olsen Sandakerveien 41, 0477 Oslo
Cadastral unit 301-225/257/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 47 units

20 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.