BIZTRAC BETA
COMPANY REGISTER PROFILE
917552460 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

JENG HOLDING AS

Org. no. 917552460 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 227,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

JENG HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 917552460. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Holdingselskap for Ali Gåsdal Jeng og annet som naturlig faller sammen med dette.”.

Key figures · 2025

Operating profit
NOK −1,000
▲ +0 %
Equity
NOK 227,000
▲ +1198 %
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns JENG HOLDING AS?

JENG HOLDING AS
· NOK −1,000 profit

JENG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JENG HOLDING AS

Who owns JENG HOLDING AS?

ALI GÅSDAL JENG is the largest registered owner, with 100.0%.

Where is JENG HOLDING AS based?

JENG HOLDING AS has its business address in Oslo.

Property

Business address Munkerudveien 48, 1165 Oslo
Cadastral unit 301-181/233/0/0
Building Tomannsbolig, horisontaldelt · 2 units

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