BIZTRAC BETA
Retail sale of motor vehicles

A-I HOLDING AS

Org. no. 923425675 Limited company (AS) Larvik Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −31,000
Equity NOK 30,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

A-I HOLDING AS is registered as a limited company in Larvik, Vestfold with organisation number 923425675. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i aksjer, andeler og fast eiendom samt rådgivning og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −31,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −31,000
Equity
NOK 30,000
Est. value
NOK 38,000

Financial health · 2024

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

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

Who owns A-I HOLDING AS?

AGON ISLAMI
A-I HOLDING AS
NOK 0 rev. · NOK −31,000 profit

A-I HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does A-I HOLDING AS own?

A-I HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Group structure

A-I HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about A-I HOLDING AS

Who owns A-I HOLDING AS?

AGON ISLAMI is the largest registered owner, with 100.0%.

What is the revenue of A-I HOLDING AS?

A-I HOLDING AS had revenue of NOK 0 in 2024.

Where is A-I HOLDING AS based?

A-I HOLDING AS has its business address in Larvik.

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.