biztrac. BETA
COMPANY REGISTER PROFILE
923035222 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

ELSO LAMA HOLDING AS

Org. no. 923035222 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2,000
Operating profit NOK −2,000
Equity NOK 337,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

ELSO LAMA HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 923035222. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering og konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2,000 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 2,000
▼ −69 %
Operating profit
NOK −2,000
▲ +89 %
Equity
NOK 337,000
▼ −0 %
Est. value
NOK 179,000

Financial health · 2025

Liquidity
71.18
Very good
Current assets ÷ current liabilities
Profitability
-0.1%
Not satisfactory
Return on total assets
Solidity
11.8%
Satisfactory
Equity as a share of total capital

Who owns ELSO LAMA HOLDING AS?

ELSO LAMA HOLDING AS
NOK 2,000 rev. · NOK −2,000 profit

ELSO LAMA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ELSO LAMA HOLDING AS own?

ELSO LAMA HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about ELSO LAMA HOLDING AS

Who owns ELSO LAMA HOLDING AS?

Lars Marius Opsal is the largest registered owner, with 100.0%.

What is the revenue of ELSO LAMA HOLDING AS?

ELSO LAMA HOLDING AS had revenue of NOK 2,000 in 2025.

Where is ELSO LAMA HOLDING AS based?

ELSO LAMA HOLDING 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 03.10.2026.

Report a problem

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