biztrac. BETA
COMPANY REGISTER PROFILE
833591452 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of automotive fuel

ELAHI HOLDING AS

Org. no. 833591452 Limited company (AS) Drammen Incorporated 2024 Active
Revenue 2025 NOK 0
Operating profit NOK −94,000
Equity NOK 1.1m
Incorporated 2024
Share capital NOK 140,000

Signals

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

ELAHI HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 833591452. The business is classified under retail sale of automotive fuel (NACE 47.300). The company was incorporated in 2024. Registered share capital is NOK 140,000, divided into 100 shares. The company's stated purpose is: “Investere i aksjer og andre virksomheter, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −94,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −94,000
Equity
NOK 1.1m
▲ +4536 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
7.91
Very good
Current assets ÷ current liabilities
Profitability
-14.5%
Not satisfactory
Return on total assets
Solidity
88.0%
Very good
Equity as a share of total capital

Who owns ELAHI HOLDING AS?

ELAHI HOLDING AS
NOK 0 rev. · NOK −94,000 profit

ELAHI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ELAHI HOLDING AS own?

ELAHI HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ELAHI HOLDING AS

Who owns ELAHI HOLDING AS?

Mahboob Elahi is the largest registered owner, with 100.0%.

What is the revenue of ELAHI HOLDING AS?

ELAHI HOLDING AS had revenue of NOK 0 in 2025.

Where is ELAHI HOLDING AS based?

ELAHI HOLDING AS has its business address in Drammen.

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.